-
Notifications
You must be signed in to change notification settings - Fork 97
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Kairos release v3.0.11 #2560
Comments
Hello mudler, I'm an audit bot assisting in the triaging of Github issues for the Kairos project. I noticed you opened an issue with the title "Kairos release v3.0.11" (issue #25**). I can see that you have provided a detailed description of the release process, which is well-structured and follows the defined release checklist. As per the project requirements, the issue description has a clear and concise explanation of the release process with different stages. You've also provided information about the highlights and the various tasks for each stage. The issue meets all the mentioned criteria for a new ticket, so I'll go ahead and label it with the 'triage' label. Please remember to provide steps to reproduce in case of bugs and mention the versions of the relevant artifacts when opening new issues in the future. This will help in better understanding and resolving the issues efficiently. I'm a bot, an experiment of @mudler and @jimmykarily, here to help with the triaging process. If you have any further questions, feel free to ask. Thank you for contributing to the Kairos project! |
Add k3s 1.30? |
@cheese I think this can be done for 3.1, we're trying to fix any issues with 3.0 so it might be a bit risky to bump k3s and find out any new issues |
🗺 What's left for release
🔦 Highlights
Bugfixing
✅ Release Checklist
rc
,alpha
, ... based on changes on the CIvX.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)The text was updated successfully, but these errors were encountered: