fix(release): enforce the #1657 peer-floor rules in the release checks
VA
6h ago+2332+2332+0123456789012345678901234567890123456789-33-33-01234567890123456789
Issue
Fixes #1657
What changed
- The 0.12.6 mobile and 0.15.5 web patch releases raised their
e2epeer floor to>=0.22.1, but no stablee2e@0.22.1ever shipped, so a fresh install of an unchanged project one2e ~0.21.3fails with ERESOLVE. The published 0.12.6/0.15.5 metadata cannot be changed, so this change does not touch it: it makes the release checks catch the next one, and corrects the floors the next releases will publish. - Rule (b),
scripts/check-peer-ranges.ts: a peer floor must name a version the sibling released (## x.y.zin its CHANGELOG.md), or the runner version in the same release (the version the sibling's pending changesets will release). - Rule (a),
scripts/check-changeset-bumps.ts: a changeset that raises a peer floor past a runner minor the previous range accepted must be a**Breaking:**minor. The previous floor is read off the package's release tag; a raise counts only when it cuts off a released version on an older minor. - Rule (c),
scripts/engine-exports.ts(new): every named import frome2eor ane2e/*entry must be exported bye2eat the floor version, read off thee2e@<version>tag. A newe2e/engineimport counts as raising the floor. - The floors move to the released versions they already meant in practice, all as patch changesets: web and mobile to
e2e >=0.23.0(first version exporting thestepTimeoutvalue and theEngineDoctorChecktypes both engines import), acp toe2e >=0.22.0(first version exporting thee2e/agentrules and tools it imports), limrun to mobile>=0.12.0(first mobile release with the provider-owned local daemon change from #988; on0.11.0the local daemon picks upAGENT_DEVICE_DAEMON_BASE_URL). None cuts off a released version a consumer could install on the old range, so no**Breaking:**minor is needed for these corrections. AGENTS.mdrelease paragraph now names the three rules and the scripts that enforce them.
Verified
Ran it locally: yes
pnpm check(full gate): exit 0pnpm run test:scripts: 206 pass, 0 fail
| Check | old tree (c74de8d0, new checks) | this branch (61c1cc92) |
|---|---|---|
node scripts/check-peer-ranges.ts | exit 1, four phantom floors: web/mobile >=0.22.1, acp >=0.21.4, limrun mobile >=0.11.1 | exit 0, 4 packages' e2e imports verified against their floors |
node scripts/check-changeset-bumps.ts | exit 0, 0 floor changes | exit 0, 4 floor changes, none a crossing raise |
Synthetic: web floor 0.18.0 to 0.23.0 with a patch changeset | not run on main | exit 1, rule (a) fires; with a **Breaking:** minor it passes |
Synthetic: web floor 0.22.0 | not run on main | exit 1, rule (c) names stepTimeout, EngineDoctorCheck, EngineDoctorInfo |
Two notes, not failures: the eight packages peering on e2e >=0.15.0 report that the floor cannot be verified from the tag record (e2e@0.15.0 was released but never tagged; earliest tag is 0.15.1). Their imports were verified present at 0.15.1, and the released-floor rule still applies to them. Rule (c) covers e2e/* imports only; an integration's imports from @e2e-dev/web or @e2e-dev/mobile are the same shape but a different sibling, and are a follow-up, not part of this change.