Package version-matched CLI documentation - #25
Merged
Conversation
README links pointed into docs that npm omitted, so installed users could not follow the documented command and recovery routes. Ship the public documentation graph with each CLI version and verify package-local links. Define latest as the supported stable release while a distinct next candidate remains limited to its named qualification.
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.
Summary
latestas supported stable while a distinctnextremains qualification-onlyVerification
npm audit: 0 vulnerabilitiesnpm run check: 154/154 tests plus typecheck, lint, format, package allowlist, and packed-package smokegit diff --check: PASSNo version, release, publication, or dist-tag state changes.