Add required --allow-publish flag to npm trust commands#31
Merged
Conversation
npm 11.17 requires an explicit permission flag on npm trust; the release workflows run a full npm publish, so --allow-publish is the right grant.
|
Firetiger deploy monitoring skipped This PR didn't match the auto-monitor filter configured on your GitHub connection:
Reason: PR modifies only documentation (docs/npm-releases.md) and does not affect any of the monitored repos (kernel, infra, hypeman, hypeship); please opt in manually if deploy monitoring is needed. To monitor this PR anyway, reply with |
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
npm trust github ...now fails on npm 11.17 with "At least one permission flag is required (--allow-publish, --allow-stage-publish)". The release workflows run a plainnpm publish, so--allow-publishis the correct grant. Updated all fournpm trustinvocations indocs/npm-releases.mdand bumped the suggested npm install to^11.17.0to match the syntax.Test plan
npm trust --helpon npm 11.17.0 confirms the flag and usage🤖 Generated with Claude Code
Note
Low Risk
Documentation-only change to release setup instructions; no runtime or workflow code is modified.
Overview
Updates
docs/npm-releases.mdso trusted-publisher setup matches npm 11.17+, wherenpm trust githubrequires an explicit permission flag.The doc now recommends
npm install -g npm@^11.17.0(was^11.10.0) and adds--allow-publishto everynpm trust githubexample for@onkernel/cua-ai,@onkernel/cua-agent, and@onkernel/cua-cli, including the post–first-publish CLI block for the CLI package.Reviewed by Cursor Bugbot for commit 253cec2. Bugbot is set up for automated code reviews on this repo. Configure here.