chore(release): launch lightpanda and testmu at 0.1.0

Closed
OK
3d ago
+4-4

@e2e-dev/lightpanda and @e2e-dev/testmu launch at 0.1.0 instead of 0.0.1.

  • Both changesets were patch, so #1176 would ship them as 0.0.1. npm reads ^0.0.1 as =0.0.1, so a project that runs npm install @e2e-dev/lightpanda would never pick up a later patch without editing package.json.
  • Both changesets are now minor and open with **Release:**, the maintainer-called release that the 0.x policy from #1145 allows (scripts/changeset-bumps.ts).
  • I edited the existing files instead of adding new ones, so the changelog still credits #1163 and #772.
  • This puts them on the same footing as @e2e-dev/smol (0.1.0) and @e2e-dev/limrun (0.2.0), which also launched on a minor.
---
"@e2e-dev/testmu": minor
---

**Release:** New `@e2e-dev/testmu` package: ...

Verified

Ran it locally: yes

  • pnpm run check:changeset-bumps: 24 pending, none an unannounced 0.x minor or major.
  • GITHUB_TOKEN=$(gh auth token) pnpm exec changeset version on this branch, then reset: lightpanda 0.1.0, testmu 0.1.0. e2e 0.21.2, web 0.15.2, mobile 0.12.3 and limrun 0.2.1 are the same versions #1176 has today. The changelog entry:
## 0.1.0

### Minor Changes

- [#1163](https://github.com/tester-army/e2e/pull/1163) [`b41afa2`](...) Thanks [@okwasniewski](https://github.com/okwasniewski)! - **Release:** New package: `lightpanda()`, ...