ci: allow retrying releases from existing tags - #11
Merged
Merged
Conversation
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.
What changed
Add a guarded
workflow_dispatchentry to rerun a release from an existing version tag without moving or deleting the public tag. Manual runs check out the requested tag, verify it matchespackage.json.version, and use the derived tag for GitHub Release creation.Why
The original
v0.1.0run failed because npm provenance rejected the repository while it was private. The repository is public now, but the original run is outside GitHub's rerun window.Validation
python3 scripts/build-classic-hosts.py --checkbash scripts/validate.shbash scripts/smoke-install.shbash scripts/scan-secrets.shgit diff --checkAll passed locally.