You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 3d0a2da
Browse filesBrowse the repository at this point in the historyBrowse files
fix(release): annotate-shipped passes over a reverted cut instead of reading it as the version commit
#25605 reverted the unpublished 18.1.0 version commit 74fa3cb, moving the
CLI back to 18.0.0. locateLastVersionCommit took that revert as the commit
that introduced 18.0.0 and, 18.0.0 being on npm, stamped every changeset the
revert restored with "Shipped in 18.0.0": 412 wrong lead lines in the
regenerated Version Packages PR #25606. A commit that moves the version back
now passes over itself and the reverted cut's span, and the walk reads the
forward cut before it. On main that is 06cab48 (18.0.0-next.5 -> 18.0.0),
which leaves the same 8 changesets unconsumed that 74fa3cb annotated.
Claude-Session: https://claude.ai/code/session_014C7q5Hm34g4EPdirar9SzN
Co-authored-by: Claude <noreply@anthropic.com>
'annotate-shipped -> a second run writes nothing': 2,
1257
1302
'annotate-shipped -> a changeset whose first body line already says Shipped in is left byte-identical': 2,
1258
1303
'annotate-shipped -> outside pre mode, where the version pass deletes what it consumes': 2,
1304
+
'annotate-shipped -> a reverted cut is not a version commit: the walk reads the forward cut before it': 3,
1259
1305
'annotate-shipped -> a depth-1 clone deepens itself to the version commit; with no reachable history it warns, annotates nothing and exits 0': 4,
1260
1306
'annotate-shipped -> no version commit, an unpublished or unreadable version, an error anywhere: a warning or a plain line, nothing written, exit 0': 5,
1261
1307
});
@@ -1645,6 +1691,49 @@ async function selfTest() {
1645
1691
'with the "release" form of the line',
1646
1692
);
1647
1693
1694
+
battery('annotate-shipped -> a reverted cut is not a version commit: the walk reads the forward cut before it');
1695
+
// The 18.1.0 shape: a 17.7.0 cut left y.md unconsumed (above); the next cut
1696
+
// (17.8.0) consumed every pending changeset, was never published, and was
1697
+
// reverted, which restored them all and moved the CLI back to 17.7.0.
'and z.md, which the revert restored but 17.7.0 never carried, is not stamped as shipped in 17.7.0',
1735
+
);
1736
+
1648
1737
battery('annotate-shipped -> a depth-1 clone deepens itself to the version commit; with no reachable history it warns, annotates nothing and exits 0');
0 commit comments