chore: restore the engines' wide e2e peer ranges after the release

Closed
OK
22d ago
+3-3
  • 640a73ef chore: release left @e2e-dev/web, @e2e-dev/mobile, and @e2e-dev/github peering on e2e at the exact canary 0.15.0-canary-20260928184528. version-packages runs scripts/restore-peer-ranges.ts after changeset version; this release skipped it.
  • check:peer-ranges fails on main and on every open PR (check job), and spec is red for the same reason.
  • This is the script's own output, nothing hand-edited. No changeset: the ranges go back to what the packages declare between releases.

Verified

Ran it locally: yes

  • node scripts/restore-peer-ranges.ts on origin/main, then node scripts/check-peer-ranges.ts and pnpm install --frozen-lockfile (lockfile unchanged)
@e2e-dev/github: e2e peer 0.15.0-canary-20260928184528 -> >=0.15.0 <1
@e2e-dev/mobile: e2e peer 0.15.0-canary-20260928184528 -> >=0.15.0 <1
@e2e-dev/web: e2e peer 0.15.0-canary-20260928184528 -> >=0.15.0 <1
peer ranges: @e2e-dev/github (>=0.15.0 <1), @e2e-dev/mobile (>=0.15.0 <1), @e2e-dev/web (>=0.15.0 <1) peer on e2e as a wide range

Devin Review