Kairos release v3.0.10

[mudler]

🗺 What's left for release

• duplicated cloud config entries after installation #2492
• Empty line in /etc/os-release breaks Ubuntu Pro #2526

🔦 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, I am an experimental bot created by @mudler and @jimmykarily. I'm here to help make sure new Github issues follow the project's rules.

Looking at your issue with the title "Kairos release v3.0.10" in the repository "kairos" owned by "kairos-io", I noticed that it doesn't meet one of the requirements: there should be a description of the issue. While the issue does provide some information, it lacks a clear description of the problem or purpose of the issue.

In order for the issue to be properly addressed and handled, please provide a detailed description of the issue you're experiencing or the goal you're trying to achieve. This will help the community understand the problem and provide more accurate guidance or solutions.

After providing a description of the issue, please make sure to specify the steps to reproduce, if it's a bug, and mention the versions of the relevant artifacts being used. This additional information will help the project's team to better analyze and triage the issue.

I've labeled your issue with the 'question' label to indicate that it needs more information. Once you provide the necessary details, someone from the community will help you further. If you have any questions, feel free to reach out.

Remember, I'm a bot, and I'm here to help enforce the project's rules. Thank you for your understanding.