panates / rman / 36542064385

95%

push

github

chore: sync the lockfile to the versions 2.0.0 wrote

`rman version` writes package.json and does not manage lockfiles, so the release
commit left package-lock.json holding 2.0.0-beta.5 for both the root and
packages/rman while their manifests said 2.0.0.

**npm does not report this - it silently reverses it.** Measured on the release
commit: `npm ci --dry-run` answered `change rman 2.0.0 => 2.0.0-beta.5` and exit
0, rather than the EUSAGE a package.json/lockfile mismatch normally raises. So
the drift does not turn CI red; it just quietly installs a tree that disagrees
with the manifests. Regenerated, `npm ci` is a no-op again.

Third time this has followed a release. The durable fix is a step after `Version`
in the release workflow that regenerates the lockfile and commits it - as its own
commit, never amended into the release commit, whose tag is already pushed.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

2896 of 3177 branches covered (91.16%)

Branch coverage included in aggregate %.

17392 of 18372 relevant lines covered (94.67%)

196.95 hits per line