Kairos release v3.0.15

[mudler]

🗺 What's left for release

• jetson orin not booting up with 3.0.9 and 3.0.10 #2559

🔦 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
    • Bump the kairos-framework image in kairos
  • CI tests are passing
  • There are no critical CVEs in our internal components
  • 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
    • Any flavor k3s
    • 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
  • Update the release with any known issues
• Stage 4 - Announcement
  • Merge docs updates for kairos and k3s version updates
  • 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)
  • Blog post announcement

[ci-robbot]

Hello @mudler, thank you for opening this issue to clarify the tasks for a Kairos release. Could you please provide more information about what each of these checks does and why they are important? Additionally, are there any specific versions of the relevant artifacts that should be used for this release?