fix(peer-range): admit the 0.1.6-alpha.2 tuple in the canonical range - #2
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
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.
The
peer-rangetripwire (canonical range admits the published dist-tags) has been failing onmaster, so every PR in this repo is blocked.Why
semver only admits a prerelease when a comparator in the same
[major, minor, patch]tuple carries one, so each new upstream prerelease tuple needs its own clause indata/peer-range.json.0.1.6-alpha.2was published without that clause being appended:What
data/peer-range.json: canonical range gains the third clause;updatedAtbumped.package.json+pnpm-lock.yaml: this package's own three@deepseek-ai/dsh-*peers re-pinned to the same range (they were the last drifters besides three out-of-batch repos).scripts/sync-peer-range.mjs: the doc-comment example shows the current OR form.test/sync-peer-range.test.mjs: the fixture's "higher-floor" peer is raised above the new floor (its intent - a real per-package requirement above every canonical floor is left alone - is unchanged).Verified locally
node scripts/check-peer-range-latest.mjs->all checked dist-tags are admitted(exit 0; was exit 1).pnpm test64/64,typecheck,typecheck:ci,verify:self-contained,verify:artifacts,buildall exit 0.node scripts/sync-peer-range.mjs --dir <plugins>now reports this repook.