This walkthrough details how Fedora 45 turns source code into installable artifacts like ISOs, cloud images, and OSTree deployments. It follows a package from a packager's dist-git push through the entire pipeline. Fedora stores package definitions in individual Git repositories at src.fedoraproject.org, managed via fedpkg which submits builds to Koji, the build system using a hub-and-spoke architecture with clean Mock chroots.

Koji organizes builds via tags with multiple inheritance. For branched releases, updates pass through Bodhi, which gates releases through testing states (pending, testing, stable) using karma thresholds and critical-path requirements. Bodhi manages Koji tags and invokes Pungi to compose update repositories.

Pungi orchestrates composes by snapshotting a frozen package set from a Koji tag, then uses comps and variants XML to define product groupings. It runs lorax to create boot.iso installer images and coordinates Kiwi, Image Builder, and OSTree for final deliverables. The document is live as Fedora 45 has not yet released; feedback is welcomed at [email protected].