-
Notifications
You must be signed in to change notification settings - Fork 543
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
Helm: upgrade rollout operator to 0.22.0 #10241
base: main
Are you sure you want to change the base?
Conversation
Signed-off-by: drfaust92 <ilia.lazebnik@gmail.com>
Signed-off-by: drfaust92 <ilia.lazebnik@gmail.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks!
@@ -41,6 +41,7 @@ Entries should include a reference to the Pull Request that introduced the chang | |||
* [BUGFIX] Fix how `fullnameOverride` is reflected in generated manifests. #9564 | |||
* [BUGFIX] Fix `extraObjects` linting with helm lint by padding with an extra new line. #9863 | |||
* [BUGFIX] Alertmanager: Set -server.http-idle-timeout to avoid EOF errors in ruler, also for zone aware Alertmanager #9851 | |||
* [CHANGE] Update rollout-operator version to 0.22.0. #10241 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can you put this after the last CHANGE
entry on line 33? We try to keep them ordered by type, then chronologically
I think the GitHub CI is stuck. It should unstick itself when you push the changelog change. |
The CHANGELOG has just been cut to prepare for the next release. Please rebase |
What this PR does
Which issue(s) this PR fixes or relates to
Fixes #
Checklist
CHANGELOG.md
updated - the order of entries should be[CHANGE]
,[FEATURE]
,[ENHANCEMENT]
,[BUGFIX]
.about-versioning.md
updated with experimental features.