Installing a Beta pre-release of Fedora puts you on the Branched release path. There may be some differences from a fresh install because the installer can do certain things slightly differently than the package update system.
If you have installed Rawhide, you would actually need to downgrade to get the final release, which is not recommended. (It might be easier to wipe the system and install from scratch.)
Alternatively, you can switch to the Branched pre-Beta release immediately after it becomes available. See Releases/Branched#Yum_update_from_previous_official_release for how to do this using dnf.
Performing the upgrade
You shouldn't need to do anything to get the final public release, other than install package updates as they become available. You can use "sudo dnf update" or wait for desktop notification.
After updating to final, I see the new fedora and updates repos, but why is my rawhide repo also still enabled?
This will happen if you have manually modified your
/etc/yum.repos.d/fedora-rawhide.repo file before updating
. For example, if you have switched from using
baseurl= for a repository definition, this situation occurs. Once
is updated, rather than overwrite your configuration changes, the new Rawhide repository file is created as
fedora-rawhide.repo.rpmnew. To disable Rawhide, either toggle
enabled=0 in your modified configuration or run the following command
sudo mv /etc/yum.repos.d/fedora-rawhide.repo.rpmnew /etc/yum.repos.d/fedora-rawhide.repo
After updating to final, why does yum complain about mismatched package versions even though my updates-testing repo is disabled?
This can happen if your updates-testing repository was enabled at any time you ran a branched release. It can also happen if you install a Beta pre-release and later upgrade to the final release. Packages in the rawhide and updates-testing repositories may not make it into the fedora or updates repositories, leaving your system stranded with newer versions than those that are in the final release.
To fix this, run this command to bring your system into sync with the final release:
sudo dnf distro-sync
I found a Fedora 40 ISO leak before release day! Is it legit or is it exploited?
The only way to know for sure is to verify the leaked SHA256SUM CHECKSUM file's GPG signature (if available) with the official Fedora GPG key. If you can't, or won't do this, it's safer to just be patient and wait for release day. Also note that even if the early leak does check out, it might not be the FINAL release. Fedora has in the past had to re-push last-minute changes to the official releases.
If I report my problem to fedora-test list or post in fedora forum, will my issues reach the developers?
You can use such avenues for discussions however for maximum efficiency, we always recommend that all actual bugs be reported to the Fedora bug tracker (Bugzilla) against the appropriate package in rawhide. This is the only assured way of reaching the right developers.
When is Fedora 40 going to be released?
An up-to-date release schedule is always maintained at this page.
What are the new features in Fedora 40?
The Fedora 40 change set page have more details.
Should I upgrade to Fedora 40?
We offer you the choice of the greatest and latest release. Per the Fedora lifecyle policy, each release of Fedora is maintained until a month after the second following release. For example, Fedora 38 will stop getting updates a month after Fedora 40 release. We highly recommend that users of unmaintained, "end-of-life" (EOL) releases upgrade to a newer release to continue getting critical security fixes.
How can I upgrade?
Refer to Upgrading.
Where can I get support for 40 pre-releases?
For IRC Support, please use the #fedora-qa channel instead of the main #fedora channel. The FedoraForum site has a dedicated forum for pre-releases; please use that forum instead of the main forum. For email list discussions, please use the fedora-test-list.