Repository navigation
fix(ci): allow the npm publish to be dispatched manually - #96
Merged
Merged
Conversation
A failed publish could not be recovered. `gh run rerun` replays the workflow file from the tagged commit, so it replays the failure too, and the job had no `workflow_dispatch` trigger to run the fixed file instead. Three releases are currently tagged on GitHub but absent from npm because of exactly this. Adding the trigger makes a re-publish possible without cutting a throwaway release. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Merged
3 of 5 tasks
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.
Follow-up to #94.
A failed publish cannot be recovered today.
gh run rerunreplays the workflow file from the tagged commit, so it replays the failure too, and the job has noworkflow_dispatchtrigger to run the fixed file instead.v0.22.2, v0.22.3 and v0.23.0 are all tagged on GitHub and absent from npm for exactly this reason. This trigger makes a re-publish possible without cutting a throwaway release.
Test plan