Repository navigation
Use npm stage publish in the npm-publish workflow - #788
Closed
Hugo-ter-Doest with Copilot wants to merge 2 commits into
Closed
Hugo-ter-Doest with Copilot wants to merge 2 commits into
Hugo-ter-Doest with Copilot wants to merge 2 commits into
Conversation
Co-authored-by: Hugo-ter-Doest <7829083+Hugo-ter-Doest@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Fix failing GitHub Actions job publish-npm
Use Oct 22, 2026
npm stage publish in the npm-publish workflow
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.
The
publish-npmjob fails withE403 (E_STAGE_REQUIRED). The registry says theNPM_SECRETtoken can only publish to a staging area, so a plainnpm publishis rejected..github/workflows/npm-publish.yml: the publish step now runsnpm stage publishinstead ofnpm publish. The command comes from the registry's error message. I haven't tried it, so please check it against npm's docs and the workflow's Node 20 setup.After a successful run the release is only staged. Someone with npm access still has to approve the staged version before it goes live. If you'd rather publish straight from CI, the token would have to be replaced with one that is allowed to publish directly.