chore(main): release 0.2.0 - #530
e2b-generated-code-auto-fixer[bot] wants to merge 1 commit into
Conversation
![claude[bot]](https://avatars.githubusercontent.com/in/1236702?s=60&v=4){kind=small}
| @@ -1,3 +1,3 @@ | |||
| { | |||
| ".": "0.1.0" | |||
| ".": "0.2.0" | |||
There was a problem hiding this comment.
🔴 Bumping the manifest to 0.2.0 breaks tests/unit/release-config.test.ts, which hardcodes expect(manifest['.']).toBe('0.1.0') at line 28. That assertion passed on the base branch (manifest was 0.1.0) and now fails on main after every release-please bump, breaking CI/unit tests for maintainers on unrelated PRs. Fix: the test must not hardcode a version string that release-please is expected to change; assert a stable invariant instead (e.g. manifest['.'] === pkg.version and a semver-format check), so future automated bumps keep passing.
Extended reasoning...
tests/unit/release-config.test.ts:24-30 reads .release-please-manifest.json and package.json and asserts manifest['.'] === '0.1.0' literally, then asserts pkg.version === manifest['.']. Before this diff both files were 0.1.0, so the test passed. This diff (a release-please automated bump) changes .release-please-manifest.json to 0.2.0 and package.json's version to 0.2.0 too, but does not touch the test file (it is not among the 3 changed files). After merge, expect(manifest['.']).toBe('0.1.0') fails because manifest['.'] is now '0.2.0', even though pkg.version and manifest still agree with each other. Any CI run of the unit test suite on main (or any branch based on main) after this merge fails on this assertion until a human manually edits the test, defeating the purpose of an automated release-please bump PR.
Verification: normal. tests/unit/release-config.test.ts:28 asserts expect(manifest['.']).toBe('0.1.0'). On the base commit (f7b85de) .release-please-manifest.json had ".": "0.1.0", so this assertion passed. This diff changes the manifest to ".": "0.2.0" (HEAD manifest confirmed) but does not touch the test file (only 3 files change: .release-please-manifest.json, CHANGELOG.md,… | normal.…
## Summary The release-config unit test asserted the manifest version is exactly 0.1.0, so it fails on every release PR, starting with #530. It now checks the version is SemVer-shaped and that package.json agrees with the manifest, which is the invariant we care about. ## Verification - `vitest run tests/unit/release-config.test.ts` passes on main and with the manifest and package.json bumped to 0.2.0 locally. Unblocks #530. Sponsor: @svalleru.
1 participant
🤖 I have created a release beep boop
0.2.0 (2026-09-16)
Features
This PR was generated with Release Please. See documentation.