Conversation
The npm stage prerequisites stated that the package must already exist on the npm registry. Staging now supports brand-new packages: staging a package that doesn't yet exist creates it when the staged version is approved. Update the prerequisites accordingly. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.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
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
The
npm stagePrerequisites section states that the package must already exist on the npm registry. Staged publishing will soon support creating brand-new packages via staged publishing.This updates the prerequisite docs accordingly.
Changes
docs/lib/content/commands/npm-stage.md— replaced the "Package must exist" prerequisite with "New or existing packages," clarifying that a package does not need to pre-exist and that approving a staged brand-new package creates it.Related
Companion docs change in npm/documentation: npm/documentation#2047 (the generated
content/cli/*/commands/npm-stage.mdxpages are synced from this file via theupdate-cliworkflow).