Prepare CLI 0.2.2 root output - #31
Merged
Merged
Conversation
Advance the backward-compatible 0.2 line for integrated current-directory root output without reusing the immutable 0.2.1 registry or tag identities. Preserve candidate publication under next and leave latest unchanged.
Exercise the installed package's current-directory materialization on POSIX and its explicit unsupported contract on Windows so the supported-platform CI matrix proves the shipped behavior.
Bind the root-output integration observation to its exact main tree and reject any candidate version already recorded as consumed. This keeps the release note durable after publication instead of teaching a transient next-version instruction.
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
Verification
Release boundary
This draft does not publish npm, create or move a Git tag, or change next/latest. Live preflight still shows next=0.2.1, latest=0.1.0, no npm 0.2.2, and no v0.2.2 tag. Trusted-publisher identity and package availability remain publication-time checks.