🔧 chore(ci): put every Helm pin on v3.21.4 - #320
Merged
Conversation
konih
enabled auto-merge (rebase)
August 19, 2026 16:33
Renovate bumped the azure/setup-helm input in release.yaml to v3.21.4 while the annotated HELM_VERSION pins stayed on v3.17.3, so the release would have packaged, pushed and signed the chart with a Helm four minor versions ahead of anything CI ever ran. release.yaml parses `helm push` output to extract the chart digest, so a format change there fails the release -- loudly, since the step exits non-zero, but only at release time. Aligns ci.yaml (x2), kind-e2e-setup, hack/install-helm.sh and Taskfile.yml to v3.21.4 so CI exercises the version the release actually uses. Also groups the pins so this cannot recur: the setup-helm input is seen by the github-actions manager and the annotated pins by the custom manager, putting them in different renovate groups. Both resolve to depName helm/helm, so a matchDepNames rule keeps them in one PR from now on.
konih
force-pushed
the
chore/align-helm-version
branch
from
August 19, 2026 16:39
ca0f090 to
829ef9f
Compare
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
|
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
1 participant
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.
The skew
#318bumped theazure/setup-helminput inrelease.yamlfromv3.17.3tov3.21.4. Theannotated
HELM_VERSIONpins stayed onv3.17.3, because they are matched by a different renovatemanager and therefore landed in a different group.
Net effect: the release would package, push and sign the chart with a Helm four minor versions
ahead of anything CI ever runs.
That matters more than a usual version skew because
release.yamlparseshelm pushoutput toextract the chart digest:
If that output format ever changes, the release fails. It fails loudly — the step exits non-zero
with
failed to extract chart digest from helm push output— but only at release time, never in CI.What this does
ci.yaml(×2),.github/actions/kind-e2e-setup/action.yml,hack/install-helm.shandTaskfile.ymltov3.21.4, so CI exercises the version the release actually uses.matchDepNames: ["helm/helm"]grouping rule so the pins move together in one PRfrom now on. Both sides already resolve to
helm/helm— theTaskfile.ymlannotation states itexplicitly (
# renovate: datasource=github-releases depName=helm/helm).Aligning up rather than reverting
release.yaml: the newer Helm is what renovate wants anyway,and this way CI validates it. If Helm 3.21 breaks chart lint or
helm unittest, this PR is wherethat surfaces — which is the point.