CapivaraOS 2.0.0 ships based on Fedora 45 with in-place upgrades

CapivaraOS, a Fedora-based Linux distribution offering GNOME, KDE Plasma, and Xfce desktop environments, has released version 2.0.0. The new version derives from Fedora 45 and introduces a continuous in-place upgrade model, allowing users to update their systems without full reinstallation. The release also adds new custom applications named Marsh, Pup, and Snout, all shipping at version 2.0.0 alongside the distribution update.

The distribution targets users who want Fedora's upstream foundation with additional desktop choice and custom tooling. By promising continuous in-place upgrades, CapivaraOS aims to reduce the maintenance burden typically associated with major version migrations on Fedora-derived systems. The three desktop options remain available, giving users flexibility in their environment selection.

What changes in CapivaraOS 2.0.0

• Fedora 45 rebase: The distribution moves its foundation from an earlier Fedora release to Fedora 45, inheriting that upstream's kernel, toolchain, and package versions.
• Continuous in-place upgrades: The release introduces a mechanism allowing users to upgrade between major versions without reinstalling, a departure from traditional Fedora upgrade paths that often require more involved migration steps.
• Custom applications: Three new tools—Marsh, Pup, and Snout—ship at version 2.0.0, representing distribution-specific software additions beyond standard Fedora packaging.
• Desktop environment selection: GNOME, KDE Plasma, and Xfce remain available as installation options, maintaining the distribution's multi-desktop approach.

Why it matters

For Fedora-derived distribution users, CapivaraOS's in-place upgrade promise addresses a long-standing pain point where rebasing or version jumps often require manual intervention or clean installs. The addition of custom applications suggests the project is building its own tooling layer atop Fedora, potentially offering a model for other derivatives seeking to differentiate while maintaining upstream compatibility. However, the sustainability of continuous in-place upgrades on a Fedora base remains to be proven in practice across multiple release cycles.