Repository navigation
docs(cli): document published GitHub registry installation - #9
Merged
Merged
Conversation
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.
The CLI is published automatically to GitHub Packages, while npmjs publishing is optional. The existing bare install instructions fail on a fresh machine when npmjs publishing is not configured.
Lead both installation guides and release notes with authenticated scoped GitHub registry setup, remove the token-in-command example, and document the actual publishing automation. Version remains 0.6.7; workflow changes are limited to release-note prose.
Validation: whitespace checks, all eight workflow Bash literal blocks pass bash -n, and byte comparison confirms publishing logic outside the release notes is unchanged.