fix(ci): pin cosign-installer to a tag that exists - #52
Merged
Conversation
The helm chart publish failed on v0.2.2 with "Unable to resolve action sigstore/cosign-installer@v4". Bumping it to a floating major was my mistake: that project publishes v4 only as exact releases, and its newest moving major tag is still v3, so v4 resolves to nothing. Pinned to v4.1.2, the current release. This one needs a deliberate bump rather than following a moving tag, because upstream does not offer one. The binary release itself succeeded; only the chart publish failed, and it can be re-run by dispatch once this lands.
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.
The v0.2.2 chart publish failed with
Unable to resolve action sigstore/cosign-installer@v4.My regression, from the action bump in #49. I moved every action to its current major based on the latest release tag, but
sigstore/cosign-installerpublishes v4 only as exact releases — its newest moving major tag is stillv3, so@v4resolves to nothing. Every other action I bumped does publish a floating major, which is why only this one broke.Pinned to
v4.1.2, the current release. This one needs deliberate bumps because upstream offers no moving tag to follow.The binary release for v0.2.2 succeeded: 7 assets and the GHCR image are published. Only the chart publish failed, and it can be re-run by dispatch once this lands.