📢 Kairos release v3.5.0

[mudler]

🗺 What's left for release

• 🔒 Confidential computing #2131
• Verified images #215
• 🔒 Image encryption #1173
• rootless k3s #371
• Deprecate reading of /etc/elemental/config.yaml #2233
• Security Hardening #111
• 🌱 Conformance tests #958
• Filesystem expansion on rpi4 doesn't work with Alpine #1995
• cgroup_memory not mounted in Alpine rpi4 #2002
• Upgrade on alpine arm errors #2135
• feat: Investigate using eroFS for our active/passive/recovery images #2896

Next release: #2129

🔦 Highlights

< top highlights for this release notes >

✅ Release Checklist

• Stage 0 - Finishing Touches
  • Check if Kairos-docs has any open PRs that need to be merged.
  • Check if osbuilder is in the wanted version/latest
  • Check if any kairos/packages were bumped. Ensure they were merged and repo updated (Dependency Dashboard kairos-framework#2)
  • Cut a new release of the kairos-framework images if any packages were bumped.
  • Bump the kairos-framework image in kairos
  • 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