Document stable CLI promotion - #23
Merged
Merged
Conversation
Record the completed 0.1.0 latest-tag promotion and make the release-completion boundary explicit. Keep future release commands version-derived and initial setup mutations out of the routine path.
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
0.1.0promotion to npm's defaultlatestchannelv0.1.0tag or package versionVerification
npm run check(151 tests plus typecheck, lint, formatting, package check, and packed smoke)npm audit(0 vulnerabilities)git diff --checklatest=next=0.1.0Boundary
This changes documentation and documentation-policy tests only. It does not change CLI runtime code, the publication workflow, package metadata, npm dist-tags, or any deployed service.