Fedora Linux 45 has branched from Rawhide, marking the point where work on the next Fedora release moves into a dedicated stabilization track. This does not mean Fedora 45 is ready for normal users yet. It means its packages and approved changes can now be tested against a separate Fedora 45 branch while Rawhide continues toward Fedora 46.
Key takeaways
- Fedora 45 branched from Rawhide on 11 August 2026, as scheduled.
- The branch is a development milestone—not the Fedora 45 stable release.
- Fedora’s approved change list includes database, networking, storage, desktop and security work.
- Individual changes can still be modified, postponed or dropped before the final release.
What branching from Rawhide means
Rawhide is Fedora’s continuously changing development stream. New compiler versions, libraries and system-wide changes normally land there first. At a scheduled point in each release cycle, Fedora creates a separate branch for the upcoming version.
That branch now exists for Fedora 45 in Fedora’s official source repositories. From this point, maintainers can focus Fedora 45 work on integration, testing and release readiness, while Rawhide remains open for development headed toward the following Fedora release.
Branching is therefore important, but it should not be confused with a beta or stable release. Fedora 45 is still under development. Packages may change, unfinished features may miss their deadlines and bugs are expected during this phase.
Eight Fedora 45 changes worth watching
Fedora’s official change set currently lists a wide range of accepted and tracked work. The table below highlights changes with practical impact for desktop users, administrators and developers.
| Fedora 45 change | Who it affects | Practical impact | Current status |
|---|---|---|---|
| MariaDB 12.3 as the distribution default | Database administrators and developers | Unversioned MariaDB packages move from the 11.8 series to 12.3. | Accepted |
| MySQL 9.7 as the distribution default | MySQL users and application developers | Default MySQL packages move from the 8.4 series to 9.7. | Accepted |
| Stratis storage in Anaconda | Server administrators and advanced installers | Installation on Stratis filesystems is planned for Kickstart and manual partitioning. | Accepted |
| IPv6-mostly support in NetworkManager | Network administrators and modern deployments | Fedora plans to enable NetworkManager support for IPv6-mostly networks by default. | 100% code complete |
Restricted ptrace by default |
Desktop and security-conscious users | Unprivileged programs receive fewer debugging permissions unless development tools restore them. | Finished |
| DRM Panic frontend | Desktop users and bug reporters | A web-based interface is planned to explain kernel panic information and help file reports. | Accepted |
| Atomic Desktop images built with image-builder | Silverblue, Kinoite and other Atomic Desktop users | Fedora plans new build infrastructure and additional image formats for supported variants. | Testable |
| New desktop secrets-service work | GNOME and KDE desktop users | The proposed default secrets provider changes from older desktop-specific services to oo7. | Accepted |
The status column matters. “Accepted” means Fedora has approved the change for the release process; it does not guarantee that every part is already complete. A feature can still be adjusted or moved to another release if it is not ready.
Database and developer changes
Two of the clearest Fedora 45 changes concern database defaults. Fedora uses versioned package layouts for MySQL and MariaDB, but one release from each family also provides the normal unversioned package names. Fedora 45 plans to make MySQL 9.7 and MariaDB 12.3 those defaults.
This does not mean an existing production database should be upgraded without preparation. Administrators need to read upstream release notes, check removed or changed behaviour, test applications and take a verified backup before moving important workloads.
Fedora 45 also tracks several high-impact platform changes. The approved Fedora 45 ChangeSet lists Python 3.15, RPM 6.1, GCC 16.2, LLVM 23 and an OpenSSL 4.0 rebase. These upgrades matter to developers because they can expose compatibility issues in packages, build pipelines and third-party software.
Other major Fedora 45 changes
The eight changes above are a focused selection, not the complete Fedora 45 list. Fedora has also approved several changes with broader user or developer impact:
- Python 3.15: Fedora’s main Python stack moves forward from Python 3.14.
- RPM 6.1 and signature enforcement: package tooling is updated, while signature checking is enforced by default unless a user explicitly overrides it.
- GCC 16.2 and LLVM 23: newer compiler toolchains affect package maintainers and software developers.
- OpenSSL 4.0: the cryptography stack receives a major rebase that may require compatibility testing.
- kmscon as the default virtual terminal: Fedora is testing a userspace console as a replacement for the traditional kernel framebuffer console.
- Reproducible package builds: Fedora continues work intended to make independently rebuilt packages produce matching results.
Approval does not mean every item is already finished. Fedora’s ChangeSet records implementation states such as accepted, testable, code complete or finished, and those states can change as development continues.
Desktop, storage and security changes
A safer default for process inspection
The restricted ptrace change is designed to stop one unprivileged process from freely inspecting another existing process belonging to the same user. That can reduce the information available to malware. Installing debugging tools can restore the broader development behaviour through a system setting, so developers are not permanently locked out.
Better kernel-panic reporting
The planned DRM Panic frontend aims to make serious graphics or kernel failures easier to understand. Instead of leaving users with an intimidating low-level failure screen, Fedora wants a web-based path that can explain the available information and help users prepare a useful Bugzilla report.
Stratis installation support
Fedora’s installer work aims to make Stratis a direct installation target. The proposal covers automated Kickstart installations and manual configuration through Anaconda’s web interface using Cockpit Storage. This is especially relevant to administrators who want storage pooling and management without assembling the layout after installation.
IPv6-mostly networking
NetworkManager’s IPv6-mostly support is intended for networks where devices primarily use IPv6 while IPv4 connectivity is supplied only when required. Enabling this by default can help Fedora operate cleanly in newer network designs without removing normal dual-stack support.
What is not confirmed yet?
A change appearing in Fedora’s tracker is not the same as a final-release promise. Some entries remain accepted but unfinished, while others are still testable or may have contingency deadlines. Package versions can also change before beta and final freezes.
For that reason, Fedora 45 coverage should separate three levels of confidence:
- Confirmed milestone: the Fedora 45 branch now exists.
- Approved release work: changes accepted for Fedora 45 but still subject to completion and testing.
- Final behaviour: known only after packages and features survive the release process.
When will Fedora 45 be available?
Branching is followed by additional testing, freeze and release-candidate work. Fedora’s official Fedora Linux 45 key-task schedule lists the Beta target for 15 September 2026 and the current Final target for 20 October 2026. These are target dates, not guarantees: Fedora can delay a milestone when blocker bugs remain unresolved.
We will update this article when Fedora publishes the beta and final release announcements.
Should you install Fedora 45 now?
Most users should wait. Fedora 45 is appropriate now for contributors, package maintainers and testers who understand that development systems may break and who are prepared to report problems.
For a normal desktop or production server, stay on a supported stable Fedora release. If you decide to test Fedora 45, use a spare computer or virtual machine, keep separate backups and avoid depending on the system for important work.
Frequently asked questions
Has Fedora 45 been released?
No. Fedora 45 has branched from Rawhide, but it is still a development release. Beta and final milestones come later.
What happens to Rawhide after Fedora 45 branches?
Rawhide continues as Fedora’s rolling development stream and begins moving toward changes intended for the release after Fedora 45.
Are all Fedora 45 changes guaranteed?
No. Accepted changes must still be completed and tested. Fedora can modify or postpone work that is not ready before release deadlines.
Comments