Fix helm dependency build
once and for all
#535
Reference in New Issue
Block a user
No description provided.
Delete Branch "refs/pull/535/head"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Description of the change
We are affected by a regression of a Helm bug from May 2023. I've tested
the Helm versions 3.13.1, 3.13.0 and 3.12.3. Both 3.13.x are affected.
3.12.3 works. So let's downgrade and drop the docker login in PR builds.
I've also switched the
apt install helm
with an officialalpine/helm
image I am using at work. Pinning the helm version and receiving updates
helps us identifying such issues in the future.
For the release workflow I was a bit more reluctant with changes, since
I cannot easily test them. That's why I just pinned the Helm version.
Renovate will provide one PR changing both files because it's the same
dependency (alpine/helm) from the same datasource (docker).
https://github.com/helm/helm/issues/12062
Applicable issues
Ah awesome! So it was not about rate limiting at all...
I was anyhow a bit confused since it worked initially and then stopped at some point.
Happy to use containers instead of host commands.
alpine/helm
is missing npm for running thecheckout
step.I think it requires a step before the
checkout
step which runsapk add --update npm
?Yep, already added.
@pat-s Build succeeds now.
I've verified that the renovate.json5 change does what it should.
Jep nice. Let's do the release WF in a separate PR.