feat: release check for prerelease dependencies #11

Merged
crapougnax merged 1 commit from feat/10-release-check into develop 2026-11-16 10:45:58 +00:00
Member

Closes #10

What

yarn release:check (bin/release-check.ts, logic in src/release/prerelease.ts):

  1. lists every dependency and resolution of package.json whose version is a prerelease;
  2. asks the npm registry whether a stable version, at least equal to the prerelease base and inside the same range, exists;
  3. prints the range to write for each replaceable one;
  4. reports the resolutions that are no longer needed;
  5. exits with status 1 while a prerelease remains, naming those without a stable release.

--write applies the replacements to package.json and leaves the lockfile to yarn install.

Documented in docs/RELEASE.md and docs/RELEASE.fr.md.

Today on develop

The command reports 9 entries (6 dependencies, 3 resolutions), none replaceable yet: the Quatrain packages concerned only have beta releases.

Not included

No CI gate. A job running the check on pull requests to main would make the rule binding; it would fail today by design, so it is left for a separate decision.

Tests

8 unit tests on the pure logic (range handling, 0.x and tilde ranges, manifest rewrite). The registry call was exercised by hand against the public registry.

🤖 Generated with Claude Code

Closes #10 ## What `yarn release:check` (`bin/release-check.ts`, logic in `src/release/prerelease.ts`): 1. lists every dependency and resolution of `package.json` whose version is a prerelease; 2. asks the npm registry whether a stable version, at least equal to the prerelease base and inside the same range, exists; 3. prints the range to write for each replaceable one; 4. reports the `resolutions` that are no longer needed; 5. exits with status 1 while a prerelease remains, naming those without a stable release. `--write` applies the replacements to `package.json` and leaves the lockfile to `yarn install`. Documented in `docs/RELEASE.md` and `docs/RELEASE.fr.md`. ## Today on develop The command reports 9 entries (6 dependencies, 3 resolutions), none replaceable yet: the Quatrain packages concerned only have beta releases. ## Not included No CI gate. A job running the check on pull requests to `main` would make the rule binding; it would fail today by design, so it is left for a separate decision. ## Tests 8 unit tests on the pure logic (range handling, 0.x and tilde ranges, manifest rewrite). The registry call was exercised by hand against the public registry. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
feat: release check for prerelease dependencies (#10)
All checks were successful
Build and Publish OCI Image / Build & Push ARM64 OCI Image (pull_request) Successful in 5m59s
1246537dd6
Add `yarn release:check`: it lists the dependencies and resolutions of
package.json whose version is a prerelease, asks the npm registry which
ones a stable release can replace, reports the resolutions that are no
longer needed, and fails while a prerelease remains. `--write` applies
the replacements to package.json.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
crapougnax merged commit e9dea4496e into develop 2026-11-16 10:45:58 +00:00
crapougnax deleted branch feat/10-release-check 2026-11-16 10:45:58 +00:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
modaka/studio!11
No description provided.