A GO verdict sounds like a starting gun. In Fedora's release process it is closer to a freeze: the October 29 Go/No-Go meeting declared the RC-1.4 build good enough to become Fedora 45 Final, and that build is the one that ships on Tuesday, November 3. Nothing in the image changes between now and release day unless something goes seriously wrong. That is the whole point of the gate, and after two NO-GOs, it is worth understanding what it actually locked in.
From two NO-GOs to a GO in two weeks
Fedora 45 was originally scheduled for October 20. On October 15 there was no candidate build ready to grade, so the release failed by default and slipped to October 27. On October 22 a candidate existed, RC-1.2, but outstanding blocker bugs kept it from shipping, and the target moved to November 3. The second NO-GO, over compromised eMudhra certificates in the trust store, is the one that explains most of the delay: a release image freezes its trust store at build time, so shipping it would have put fresh installs in the position of trusting keys the industry had already disowned.
RC-1.4 is the answer to that problem, and a deliberately small one. Against RC-1.3 it differs in exactly two ways: one extra stratisd patch for multi-disk encrypted installs, and a fix that had slipped out of RC-1.3. Nearly every RC-1.3 test result carries over, with the Stratis tests the single exception. That narrow diff is good news for anyone upgrading: the build that passed the gate is not a fresh, untested compose, but a known build with two targeted changes on top.
What ships in Fedora 45
Fedora Workstation ships GNOME 51, and the KDE Plasma edition ships Plasma 6.8.1, on the Linux 7.2 kernel. The console moves from the in-kernel fbcon to KMSCON, a userspace text console, and the DRM Panic front-end gives kernel crashes a cleaner on-screen presentation. Stratis becomes a native target in the Anaconda installer for the first time, and Atomic Desktops move to the WebUI installer over HTTPS.
On the security side, RPM package signature checking is now enforced by default, and ptrace is restricted for unprivileged users. The toolchain moves in step: Python 3.15, Go 1.27, GCC 16.2, glibc 2.44, LLVM 23, and RPM 6.1. One change deserves a pre-upgrade check on servers: Podman 6 drops slirp4netns and cgroups v1, so containers or tooling that still depend on either need a plan before you upgrade, not after.
How to handle Tuesday
If you run Fedora 44, the sensible move is boring on purpose. Wait for the official release announcement on Tuesday rather than chasing RC images early, then upgrade in this order: back up first, disable or update third-party repositories second, and only then run the system upgrade. The Ubuntu 26.10 upgrade checklist is a good template for that discipline even though the commands differ, because the failure modes are the same: a backup you never tested, a third-party repo that breaks the transaction, and an upgrade started at the worst possible hour.
If you already run Fedora 45 Beta or an RC, you are essentially there: keep applying updates and you will converge on the release build. If you are on Fedora 43, the date that matters has not changed: 43 reaches end of life in early December 2026, so use the extra weeks to plan rather than rush. And if you manage servers, treat the release week like any other staged rollout: upgrade one non-critical machine first, confirm services and containers behave, and only then roll the rest forward. The OpenSSL 4.1 upgrade playbook covers the same class of chore, staged and verified rather than done in one leap.
Why the delay was the feature, not the bug
It is tempting to read two NO-GOs as a project in trouble. Read them the other way: a release gate that refuses to ship a compromised trust store, and then refuses again until the fix is verified, is a gate doing exactly what it exists to do. Fedora 45 arrives two weeks late with a build that was graded twice over. That is a better trade than an on-time release that starts life with a known-bad certificate store.
Tuesday, November 3, is now the date to put in the calendar, with RC-1.4 as the build to expect. Watch for the official announcement, verify the image you download, and upgrade on your schedule, not the release clock's.
Sources: daily.dev, Fedora Linux 45 Shipping Next Week On 3 November · Linux Compatible, Fedora Linux 45 RC-1.4 Release Candidate · TechBarrista, Fedora Linux 45 Arrives November 3 With GNOME 51
