Download only the packages from the CI run - #40
Merged
Conversation
gh run download took every artifact, and docker/build-push-action uploads a build record that does not extract -- "zip: not a valid zip file". The whole 1.0.0 release failed on an artifact it never wanted. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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 1.0.0 release failed here, so nothing was published — no tag, no packages,
no image.
VERSIONis still1.0.0and nov1.0.0tag exists, so merging thisruns the release again and it goes out.
gh run downloadtook every artifact of the CI run. Since the containerimage build landed,
docker/build-push-actionuploads a build record of itsown, and that one does not extract. The release asked for the packages and was
handed something else alongside them.
Latent since the image was added, and only reachable at release time — the CI
that produces the artifacts is green either way, so nothing before the merge
could have caught it. The last release that worked, v0.75.0, predates the image
build: one artifact, no ambiguity.