feat: add optional version input to node-trusted-publish#173
Merged
Conversation
Allows callers to override the package version at publish time via `npm version --no-git-tag-version` before build/publish. Backward compatible (default empty = publish the committed version). Enables prerelease/beta publishing where the version is computed in the caller (e.g. `1.0.0-beta.42`) rather than committed to the repo. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Contributor
🛡️ SHA Pinned Actions Report✅ All 28 file(s) passed — actions are allowed and pinned as required. |
jesspanni
approved these changes
Jul 8, 2026
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
2 participants
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
Adds an optional
versioninput to the reusablenode-trusted-publish.ymlworkflow. When set, the package version is overridden before build/publish vianpm version <version> --no-git-tag-version --allow-same-version.Why
Enables prerelease/beta publishing where the version is computed by the caller at publish time (e.g.
1.0.0-beta.42) rather than committed to the repo. Callers can pass a computed prerelease version plustag: betato publish a beta from an ordinary merge, without polluting the repo history with prerelease version bumps.Compatibility
Fully backward compatible — the input defaults to
'', in which case the committed version is published exactly as before.🤖 Generated with Claude Code