feat(stage): display staged package status - #9898
Open
joelverhagen wants to merge 1 commit into
Open
Conversation
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: e928b867-eb5b-4dff-a0ec-0fdcbe278846
nishantms
approved these changes
Aug 21, 2026
martinrrm
approved these changes
Aug 21, 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
3 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.
What / Why
The stage API can return a lifecycle status for staged package versions. Display that status in human-readable output for both
npm stage listandnpm stage viewso users can tell whether staged versions are still validating or ready for review.Status values are treated as opaque server-provided values, so future statuses are displayed without requiring a CLI update. JSON output continues to preserve the returned status unchanged.
Screenshots
nom stage listshowing onestagedand onevalidating. The status values are originated from the package feed.stagedis the current default status, meaning it is ready for approval.validatingmeans it's undergoing automated checks and can't be approved yet. The lifecycle and requirements for approval are managed solely by the registry. The CLI just surfaces asstatusvalue is present in the response.The status also shows on the
nom stage viewcommand.Testing
npx tap --no-coverage test/lib/utils/key-values.js test/lib/commands/stage/list.js test/lib/commands/stage/view.jsnpm run lint -- --quiet