fix(release): fold the unpublished 0.11.3 into 0.12.0 - #426
Merged
Merged
Conversation
#358 (chore: version packages) consumed 17 changesets into a 0.11.3 CHANGELOG section and bumped to 0.11.3, but the publish job was never approved, so 0.11.3 never reached npm. Its changes first ship in 0.12.0, so their notes belong there. This reverts a1ad90f: the changesets come back, the 0.11.3 section goes, and the version returns to 0.11.2, which the release PR then bumps to 0.12.0 with every change listed. This reverts commit a1ad90f.
…0.12.0 The feedback-survey note named 0.11.3 and is renamed to match; the Vale config schema note drops a sentence justifying its patch bump against 0.11.3, moot now that the release is minor. Two survey comments follow.
The ledger's "Migrating to 0.11.3" section named a version that never shipped; its entries ship in 0.12.0 and move under that heading. 0.12.0 also had no ledger entry for the v2 API: pre-v2 runtime rules must be regenerated, an edited or copied issued rule fails check and is repaired with rule restore, rule create --json prints requestId, and init applies migration 10.
Only migration 10 applies to every project; check refuses to run until it is applied, logged in or not. The v2 entries (pre-v2 runtime rules, edited and copied rules, rule create's requestId) matter only when info --json reports loggedIn: logged out, nothing is reconciled and runtime rules are skipped as before.
Instead of preconditions on login state, run check --json once after init and act on the messages it prints: a copy of an issued rule, an edited rule, a pre-v2 runtime rule, a missing rule. A run where signatures do not apply (logged out, an expired token, an uncovered repository) prints none of them, so there is nothing to decide up front.
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.
0.11.3 was versioned but never published. The release PR #358 consumed 17 changesets into a 0.11.3 section of
packages/cli/CHANGELOG.mdand bumped the version to 0.11.3, but its publish job was never approved, so npm'slatestis still 0.11.2. Those changes first reach users in 0.12.0, but their notes sat under a 0.11.3 heading. The pending release PR (#407) showed only the 0.12.0 section and linked "Compare with v0.11.3", a tag that doesn't exist.What changes
a1ad90f).v0.11.2.mainno longer holds a version npm lacks, so pushes stop queuing publish jobs for it.patchbump against 0.11.3, which is moot now that the release isminor.agent updateledger a 0.12.0 section.initonce for migration 10, whichcheckrequires logged in or not.check's own output, not by login preconditions: runcheck --jsononce and act on what it prints (a copy of an issued rule, an edited rule, a pre-v2 runtime rule, a missing rule). A run where signatures don't apply prints none of them.rule create --jsonprintingrequestIdis noted for scripts.Checks
pnpm typecheckandpnpm lintpass, and so does the CLI suite (112 files, 1,898 tests).openspec validate --all --strictpasses (30).pnpm changeset statusreports oneminorbump for@taskless/cli, so 0.11.2 goes to 0.12.0.