📢 Kairos release v3.2.0

[mudler]

🗺 What's left for release

• Change ukify binary validation #2177
• Change validation of stub and efi files to be platform agnostic #2178
• Add UKI test in enki repo #2173
• 🐛 Alpine standard ISO does not boot on metal #2464
• UKI: Upgrade of other booting entries #2385
• Make XBOOTLDR partition work (optionally) #2287
• chore: Remove Ubuntu 23.10  #2481
• Merge oci2sysext with enki https://github.com/kairos-io/oci2sysext (or documentation) #2631
• [Spike] Make UKI systemd sysext solution more robust #2630
• Upgrade systemd-boot and systemd-ukify (if still used) to v256 #2632
• spike: LUKS partitions mounted by Kairos don't support TRIM #2693
• Filter uki upgrade releases for non-uki systems, and viceversa #2710

Rpi known issues

• 🐛 reset from the GRUB menu on alpine, gets stuck in an endless loop #2136
• It's not possible to login on an Alpine 3.19 RPi #2439
• [RPI] EFI booting no longer supported on kernels shipped with ubuntu > 22.04 #2249

Next release: #2127

🔦 Highlights

< top highlights for this release notes >

✅ Release Checklist

• Stage 0 - Finishing Touches
  • Check if Kairos-docs were updated and consider tagging them with the same version as Kairos
  • Check if osbuilder is in the wanted version/latest
  • Check if any kairos/packages was bumped and they were merged and repo updated (https://github.com/kairos-io/packages)
  • Check latest repository update was merged, otherwise trigger its job (https://github.com/kairos-io/kairos/actions/workflows/bump_repos.yml)
  • Make sure CI tests are passing.
  • Consider cutting an rc, alpha, ... based on changes on the CI
• Stage 1 - Manual testing
  • How: Using the assets from master, make sure that test scenarios not covered by automatic tests are passing, and that docs are still aligned
    • Fedora flavor install, and manual upgrade works
    • Any flavor interactive install
    • Any flavor recovery reset
    • ARM images (openSUSE, alpine) boots and manual upgrade works
    • ARM images passive and recovery booting
    • ARM images reset works
    • ARM images /oem exists
• Stage 3 - Release
  • Tag the release on master.
  • Create a branch vX.Y.Z on the docs (not tagging), so the new release can be built and displayed on the menu. Ideally open a PR so we can review and add/remove some commits if needed (in case we have documented WIP which is not available on the given release)
• Stage 4 - Announcement
  • Blog post announcement