Repository navigation
Fixed: release run failing after staging because the summary step had no npm login - #2
Merged
Merged
Conversation
PetromirDev
marked this pull request as ready for review
October 6, 2026 13:48
superKalo
approved these changes
Oct 6, 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.
Every release run goes red after the package is staged on npm, even though staging worked and the version is waiting for approval (since v1.0.0). The run summary that should tell a maintainer what to approve never gets written. For example, the v1.0.1 run staged
1.0.1and then failed. Now the run passes and its summary shows the stage id with thenpm stage viewandnpm stage approvecommands to run.What we did
In a GitHub Actions run, only
npm stage publishtrades the run's OIDC token for an npm token. The summary step then rannpm stage listwith no npm login, so the registry answered E401. This came in withaea0d6b, which moved releases to staging. The "Stage" step now runsnpm stage publish --jsonand keeps the result, and the summary step readsstageIdfrom it withjqinstead of calling npm. The README now says the run summary gives the stage id and the approve commands.