Repository navigation
Commit 32529c2
committed
chore(release): move dev's version line past the published channel
dev's package.json said 2.24.2 while main and the npm latest tag were both
2.26.0. The 2.25.0 and 2.26.0 bumps were made on release branches that merged
only to main and never came back, so dev has been trailing the published
channel by two releases.
That blocks promotion rather than corrupting it: assertChannelVersionMovesForward
in scripts/release.ts reads the live dist-tags and refuses a candidate that does
not move the channel forward, so a promotion from this range would have failed
at the release step with "dev's package.json may trail the latest release."
Found by a pre-promotion audit, not by hitting that error.
2.27.0 rather than 2.26.1, because the range carries user-visible behavior
changes and not only fixes: proxy env baked into installed service definitions,
service definitions written owner-only, the native-main fence learning to
re-ask, and the deferred tool catalog work.
No other file carries the version — the GUI package is 0.0.0 and is not
published — so this is the whole reconciliation.
Verification: tsc --noEmit exit 0; ci-workflows and repo-hygiene 143 pass /
0 fail. The version itself is checked by the release workflow against the live
registry at dispatch time, which is the only place that comparison is real.1 parent 890d339 commit 32529c2
1 file changed
Lines changed: 1 addition & 1 deletion
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
1 | 1 | | |
2 | 2 | | |
3 | | - | |
| 3 | + | |
4 | 4 | | |
5 | 5 | | |
6 | 6 | | |
| |||
0 commit comments