Repository navigation
Add a GitHub Actions button for staged npm releases - #15
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
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.
Maintainers currently need to edit version files and push a tag to stage an npm release. Add Run workflow to Stage npm release, with patch/minor/major choices (patch by default).
The manual path requires master, updates package.json and package-lock.json with npm version, runs tests and package checks, atomically pushes the version commit and tag, then stages npm in the same run. This avoids relying on another workflow being triggered by GITHUB_TOKEN's tag push. Existing v* tag releases remain supported. npm approval with 2FA remains the final publishing step.
Includes release concurrency, a timeout, and README instructions covering branch protection and staging failure recovery. No package version is changed by this PR and no release has been started.
Validation: actionlint passed; Node.js 26 npm ci, all 11 test files, and npm pack --dry-run passed. Verified patch/minor/major produce 2.2.4/2.3.0/3.0.0, matching tags and clean commits without changing locked dependencies in disposable repositories. Actual npm staging requires running the workflow after merge.