Repository navigation
Allow the release workflow to be run by hand - #7
Merged
Merged
Conversation
1.4.0 was merged to main during a GitHub Actions outage. No workflow ran for the merge, GitHub does not backfill missed runs, and with only a push trigger the only way to release was to push another commit to main purely to make something happen. workflow_dispatch is safe here for the same reason the push path is: the job skips when the tag for package.json's current version already exists, so running it by hand can rescue a missed release but can never double-publish one. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018fw9DsmQqKxkhh9vbXmyqs
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.
1.4.0 was merged to main during a GitHub Actions outage. No workflow ran for the merge, GitHub does not backfill missed runs, and with only a
pushtrigger the only way to release was to push another commit to main purely to make something happen.workflow_dispatchis safe here for exactly the reason the push path is: the job skips when the tag forpackage.json's current version already exists. So running it by hand can rescue a missed release but can never double-publish one.Merging this also fires the push trigger, which is what finally publishes 1.4.0 (the PNA fix in #6).
🤖 Generated with Claude Code
https://claude.ai/code/session_018fw9DsmQqKxkhh9vbXmyqs