ci(node): publish scoped npm packages with public access#13
Merged
Conversation
`napi pre-publish` publishes the per-platform packages with `npm publish` and no `--access` flag, so the scoped `@c3-oss/*` packages defaulted to restricted and hit `402 Payment Required`. Set publishConfig.access=public on every platform manifest (and the main package) so they publish publicly. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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
1 participant
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.
napi pre-publishrunsnpm publishin eachnpm/*platform dir without an--accessflag, so the scoped@c3-oss/codexcw-*packages were treated asrestricted (private) and failed with
402 Payment Required. The main packagealready passed
--access publicon the CLI, but the platform packages did not.Adds
publishConfig.access = publicto every platform manifest and the mainpackage. Nothing was published before the failure (E402 hit the first platform
package and aborted), so npm 0.1.0 is still clean.
🤖 Generated with Claude Code