Conversation
#799 bumped azure/setup-helm to v5.0.1 on 2026-09-07. A day later #796 added a new "Install Helm" step to release-please.yml and carried the v5.0.0 SHA over from an older branch, so that one call site has been a release behind ever since. Renovate pins by commit SHA and had already closed #799 for these versions, so it never revisited the new occurrence. The chart release job now installs the same Helm as chart-ci, pr-chart and publish-chart. Signed-off-by: Prasanth Baskar <prasanth@8gears.com>
|
Warning Review limit reachedNext included review available in 49 minutes. View limit detailsLimit details: You’ve used the included review currently available. You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Review configuration: ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (1)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Contributor
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.OpenSSF Scorecard
Scanned Files
|
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
Contributor
|
This change may need patch-release backports. Comment with one of these commands to open a cherry-pick PR:
|
bupd
added
prio/P1
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
release-please.ymlinstalls Helm a release behind every other workflow thatinstalls Helm.
How it drifted
#799 moved
azure/setup-helmto v5.0.1 on 2026-09-07, covering the three callsites that existed then. #796 landed the next day and added a new
Install Helmstep to the chart release job, carrying the v5.0.0 SHA over from a branch that
predated the bump.
Renovate pins by commit SHA, and it had already closed #799 for these versions,
so the occurrence that arrived afterwards was never revisited. It will be caught
on some future v5.0.2, but until then the job that publishes the chart is the one
running the older Helm.
Change
The chart release job now installs the same Helm as the three workflows that
lint, preview and publish the chart. One line, same SHA and comment already in
use elsewhere in the tree.
Found while checking what of #805 main is still missing — the answer is nothing
except this, which #805 does not carry either.