At the Flock 2026 Birds of a Feather session, poetically named FFFwF (or, for us lazy people, Forging Fedora’s Future with Forgejo), we discussed the current state of our migration effort to the new forge. I asked the obligatory question: Who still has things on pagure.io?!
A few brave contributors raised their hands, some with an uneasy look in their eyes. Miro swiftly pointed out that everybody is affected by one particular repository; looking at you, `fedora-scm-requests`. Luckily, the RelEng folks have it in their sights. Sure, there are a few other repos lying around the old faithful, but it is time for the Fedora Project to move on and embrace the Forge.
Our new home is currently running on the LTS branch in v15.0.2. We are going to stick with it in production, and our next LTS upgrade will be to v19.
What is going to happen next?
Pagure itself as a project is hosted on pagure.io, and that service is going to be decommissioned at the end of July 2026. What does that mean for you? Well, that depends on when you are reading this.
If you just came back from Flock 2026 and you still have active repositories on pagure.io, here is what you need to do:
- Check out the existing organizations in the Forge. If your project fits into any of the existing ones, ask its owners for a migration.
- If it doesn’t fit, open a ticket with the forge team, and we will help you decide the best path forward.
Some of us have commits in projects that point back to pagure.io. Don’t worry, we are not going to break your links, for foreseeable future. We will explore options for implementing redirects so your historical links successfully point to their current locations.
The best way to handle the transition after your move, right now, is to inform your users about your new home. Add a BIG BOLD ANNOUNCEMENT to your README, close all open issues, and create a single pinned issue with your migration announcement.
Note: Do not expect to be able to log in to pagure.io after July 2026.
Wait… and what about `dist-git`?
Well, that is the next target in the scopes of the Forge team. As I showed you in the room, we have 11 Features that define the transition. The biggest task at hand is a bit more sneaky. We are missing multiple enhancements to the upstream project that will require a lot of coordination and Go code. So, if you find yourself in possession of spare cycles and a particular need to help us make it better and faster, Forgejo is waiting for you!
A road-map with all the tasks for the move will land in the Forge soon. (See resource list below.)
Important Links & Resources
- Check out the new home: Browse existing organizations on the new Fedora Forge
- Want to write some Go? Contribute to the upstream Forgejo project.
- Track our progress: Migration roadmap will be posted here soon
AI Disclaimer: Grammar and formatting were done with the help of robots; all the original brain-farts are my own.
It would be helpful if “open a ticket with the forge team” were a link so that people can easily know where to open said ticket.
I think from the links at the bottom it’s probably Making sure you're not a bot! ?
Good point, Ben. I intended to add that but it slipped my mind amidst other things.
The link has been added.
Thank you.
This was so sad. I really liked Pagure.io. I was using it until the end.I wish I would have known about the extention to July earlier.
My bad for including a link that requires you to be logged into Codeberg. I didn’t realize you need to be logged in to filter issues by labels. Here is the upstream tracker. The link from the article uses the labels
bug|confirmedandgood first issue.I understand the sentiment around Pagure. However, the project’s codebase has some severe issues that require continuous patching. Having the backing of an actively developed project that we can also contribute to puts the Fedora Project in a much stronger position.