fix(release): publish with gh CLI, assert asset count, manual re-verify of a tag - #25
Merged
Conversation
…e-verify of a tag The v0.12.1 tag run uploaded all assets but softprops/action-gh-release failed on a post-upload metadata call (Not Found), leaving the release as a draft with one Sigstore bundle missing and the verify job skipped. - Publish step now uses gh release create/upload/edit: idempotent on re-run, sequential uploads, asserts published asset count == files in dist before un-drafting. - workflow_dispatch with a tag input runs verify against an already-published release (build skipped). - RELEASE_TAG env replaces GITHUB_REF_NAME throughout.
…ill be re-cut to include it)
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.
Why
The v0.12.1 tag run (33678952485) uploaded all 22 assets, then
softprops/action-gh-releasefailed on a post-upload metadata call (Not Found), leaving the release as a draft with one Sigstore bundle missing and theverifyjob skipped.What
gh release create/upload/edit: idempotent on re-run, sequential uploads, asserts published asset count == files indist/before un-drafting.workflow_dispatchwith ataginput runsverifyagainst an already-published release (build skipped).RELEASE_TAGenv replacesGITHUB_REF_NAMEthroughout.docs/install.mdnote the manual re-verify.Workflow-only; no runtime code. YAML validated locally.