chore(changeset): launch @e2e-dev/browser-run on a release minor
Merged
OK
4d ago+7+7+0123456789-3-3-0123456789
New packages launch on a **Release:** minor (0.1.0), not patch 0.0.1, since ^0.0.x pins exactly. Split out the @e2e-dev/web CDP header patch into its own changeset so the **Release:** summary only covers browser-run.
Merge only after @e2e-dev/browser-run@0.0.0 is on npm with a trusted publisher on release.yml and a nightly proves OIDC, so #1590 can publish it.