Yes! I had to go to the kinoite.fedoraproject.org site to actually see there is an update.

Once its release, why doesnt rpm-ostree update rebase to the next release? I have no idea of Fedora update cycles, is F37 still supported with backported updates and all? Then it could make sense. Also a setting to wait for x releases until you rebase could make sense, as it seems F38 has currently some big issues, which is always the case but should be possible to avoid on "the just work machine".

Still it has to be just an update to rebase to the next version, as only that can even be manually enabled. So as long as this is not implemented, you cant install Kinoite on a random persons PC, as they wont get upgrades.

Thanks for the Distro! I actually took the opportunity and switched to kinoite-main from ublue, lets see!

I wonder why there hasn't been an initiative in Fedora more broadly to adopt Snapper (or something similar) since we adopted Btrfs in F33, to make rolling back from borked updates much easier.

Discover will suggest to rebase to the next version once the metadata for Fedora release is updated. For now this happens a bit after the release so you don't get notified immediately but a few days after the release.

If you're using custom container images (anything uBlue), then Discover can not guess when to rebase so you're responsible for major version updates.

Updated https://fedoraproject.org/wiki/Changes/KDEKinoiteAutoUpdateByDefault to be for Kinoite only for now

Deferring this to Fedora 40 as I've been unable to complete the QA/fixes work required for it.

Deferring this to Fedora 41 as I've been unable to complete the QA/fixes work required for it.