fix!: default opts.access to null to preserve registry behavior#9419
Merged
Conversation
Closes #9414. BREAKING CHANGE: `opts.access` now defaults to `null` instead of `'public'`. With `null`, libnpmpublish no longer sets an explicit access level in the publish payload, so new scoped packages are created as `restricted` (registry default) and republishes preserve the existing access level. Callers that want to force public access must now pass `access: 'public'` explicitly.
Contributor
|
Thank you for fixing a Gar-from-the-past oversight here. |
nishantms
approved these changes
May 28, 2026
Contributor
|
Question: This change would mean that people who currently use staged publishing would get an error?
They'd need to do:
|
Contributor
Author
follow up for later readers - this isn't making it required, it just defaults to null. No changes needed for staging |
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
4 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.
Closes #9414.
BREAKING CHANGE:
opts.accessnow defaults tonullinstead of'public'. Withnull, libnpmpublish no longer sets an explicit access level in the publish payload, so new scoped packages are created asrestricted(registry default) and republishes preserve the existing access level. Callers that want to force public access must now passaccess: 'public'explicitly.