Skip to content
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

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

DrFaust92
Copy link

What this PR does

Which issue(s) this PR fixes or relates to

Fixes #

Checklist

  • Tests updated.
  • Documentation added.
  • CHANGELOG.md updated - the order of entries should be [CHANGE], [FEATURE], [ENHANCEMENT], [BUGFIX].
  • about-versioning.md updated with experimental features.

@CLAassistant
Copy link

CLAassistant commented Dec 16, 2024

CLA assistant check
All committers have signed the CLA.

@DrFaust92 DrFaust92 marked this pull request as ready for review December 16, 2024 00:23
@DrFaust92 DrFaust92 requested a review from a team as a code owner December 16, 2024 00:23
@DrFaust92 DrFaust92 changed the title bump helm rollout operator to 0.22.0 Helm: upgrade rollout operator to 0.22.0 Dec 16, 2024
Copy link
Contributor

@dimitarvdimitrov dimitarvdimitrov left a 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
Copy link
Contributor

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

@dimitarvdimitrov
Copy link
Contributor

I think the GitHub CI is stuck. It should unstick itself when you push the changelog change.

@chencs
Copy link
Contributor

chencs commented Dec 20, 2024

The CHANGELOG has just been cut to prepare for the next release. Please rebase main and eventually move the CHANGELOG entry added / updated in this PR to the top of the operations/helm/charts/mimir-distributed/CHANGELOG.md document. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants