Fedora Introduces Fedora Forge, Plans Full Pagure Migration by 2026

After nearly a year of planning and development, the Community Linux Engineering (CLE) team has officially introduced Fedora Forge, a new platform powered by Forgejo. This marks an important step forward for Fedora’s infrastructure. While Pagure has served the community reliably for many years, the project is now moving away from its in-house solution toward a more modern and scalable alternative.

The complete transition is scheduled to take place during Flock to Fedora 2026, and project maintainers are strongly advised to migrate their repositories well in advance of the event. This migration is part of a larger effort to modernize Fedora’s infrastructure. By the time Fedora 46 is released in 2027, all remaining Pagure instances, including those used for package source repositories, are expected to be fully retired. Early adoption of Fedora Forge will help teams prepare for this broader transition across the ecosystem.

For users currently relying on pagure.io, migration is now essential. Project owners are required to move their repositories before June 2026. To assist with this process, detailed migration documentation has been made available, ensuring users can transition smoothly even if they are unfamiliar with the changes.

Unlike its predecessor, Fedora Forge has a more clearly defined purpose. Pagure previously functioned as a general-purpose hosting platform, accommodating a wide range of repositories, including personal and unrelated projects. In contrast, Fedora Forge is designed specifically to support the Fedora Project itself. It is intended to host infrastructure-related code, release engineering tools, governance resources, and software developed primarily for Fedora. Projects such as deployment scripts, packaging tools, team collaboration spaces, and Fedora-focused applications fall within its scope.

On the other hand, personal repositories, hobby projects, and general upstream software are no longer suitable for this platform. Developers working on broader open-source applications are encouraged to use external services like GitHub, GitLab, or Codeberg for primary development, even if their software is packaged for Fedora. Exceptions may exist for key ecosystem tools, but these require approval through a formal request.

Migrating early provides several advantages. It helps avoid last-minute congestion and gives teams sufficient time to adapt their workflows to the new environment. Automation scripts and integrations will need to be updated to work with the Forgejo API, including adherence to rate limits and proper identification through user-agent strings. Continuous integration pipelines should also be tested, as Forgejo Actions rely on shared resources and impose a maximum runtime limit of ten minutes per job. Additionally, repository sizes should ideally remain below 500MB, with larger assets managed באמצעות Git LFS.

Although Fedora Forge aims to replace Pagure, it does not yet offer complete feature parity. For example, certain capabilities, such as private issues within public repositories, are not currently implemented in the same way. The CLE team is actively collaborating with the Forgejo community to address these gaps and improve functionality over time.

The migration process will occur in phases. Before Flock 2026, teams are encouraged to proactively move their projects, while inactive repositories may be automatically archived after six months of inactivity. During Flock 2026, the final switch will take place, after which pagure.io will remain accessible only as a read-only archive for historical reference.

Additional improvements are also underway. The Fedora Council is currently reviewing a draft usage policy that will define how the new platform should be used across the project. Community feedback will be invited before the policy is finalized.

From a technical perspective, authentication within Fedora Forge is integrated with the Fedora Account System using OIDC, allowing permissions to align automatically with team memberships. However, existing Pagure API tokens will not carry over, requiring users to generate new credentials and update their automation scripts accordingly. Repository URLs will also change after migration, meaning developers must update their Git remotes to point to the new Forge instance.

The migration tools are designed to preserve key project data, including pull requests, issues, and their relationships, with Pagure-specific tags converted into Forgejo labels. In cases where migration issues arise, the CLE team is available through dedicated support channels, including the Fedora Infrastructure Tracker and Matrix chat rooms.

Overall, Fedora Forge represents a significant evolution in how the Fedora Project manages its development infrastructure, offering a more focused, modern, and scalable platform for the future.