ci(node): add npm release workflow draft (#111) - #113
Merged
Conversation
This was referenced Feb 24, 2026
midagedev
marked this pull request as draft
February 24, 2026 08:43
midagedev
force-pushed
the
feat/node-release-workflow-111
branch
from
February 24, 2026 08:47
5be1603 to
1f45281
Compare
midagedev
marked this pull request as ready for review
February 24, 2026 08:47
Owner
Author
|
Review note: workflow_dispatch currently allows publish=true with an empty version input, which can accidentally publish the development package version. Please enforce explicit version input when manual publish is requested. |
Owner
Author
|
Follow-up patch applied:
|
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.
Summary
workflow_dispatch+node-v*tag)Notes
#107because the verify job expects workspace package files.npm publishonly executes whenNPM_TOKENexists and publish trigger is enabled.Issue
Closes #111
Part of #106
Depends on #107