Repository navigation
ci(release): skip the GHCR mirror when the chart version is already there - #172
Merged
Merged
Conversation
…here A Chart.yaml change without a version bump (#171 removing the release-please markers) re-ran Release: pack-release skipped the existing nebari-apps-0.1.0, but mirror-oci pushed the same tarball again and moved the 0.1.0 tag in GHCR to a new digest. pack-release has no output saying it skipped, so the mirror job asks GHCR itself. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Ap1Tqx1QLHRGVVSXdxeduM
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
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.
Merging #171 touched
charts/nebari-apps/Chart.yamlwithout a version bump, so Release ran.pack-releaseskipped the existingnebari-apps-0.1.0, but the Mirror chart to GHCR job pushed the same tarball again and moved the0.1.0tag to a new digest (sha256:0b38f02c…→sha256:496488f3…; the content is the released tarball, buthelm pushstamps a new manifest).The mirror job now checks GHCR first (
helm show chart … --version <version>, after the registry login) and skips the push when the version is already there. Any other failure of that check still pushes, so a real release never loses its mirror.pack-releaseat the pinned commit exposes no outputs, so the job can't use the release job's result instead.Checked:
helm show chartagainst GHCR exits 0 for0.1.0and 1 for9.9.9; actionlint 1.7.12 passes onrelease.yaml.🤖 Generated with Claude Code
https://claude.ai/code/session_01Ap1Tqx1QLHRGVVSXdxeduM