Align release preflight with CI checks

This commit is contained in:
murashit 2026-06-20 08:49:34 +09:00
parent b14969cbfb
commit 1914e986ed
2 changed files with 2 additions and 2 deletions

View file

@ -20,7 +20,7 @@ jj git push --remote origin --bookmark main
git push origin X.Y.Z
```
`release:prepare` updates the version files and creates a `## Changes` release notes template. `release:preflight` verifies the local Jujutsu/Git state, release metadata, lockfile, and full build once after the release commit is on `main`.
`release:prepare` updates the version files and creates a `## Changes` release notes template. `release:preflight` verifies the local Jujutsu/Git state, release metadata, lockfile, and the same non-cached `npm run check:ci` validation used by CI after the release commit is on `main`.
Release notes should normally include only user-facing changes. Internal implementation changes, validation details, and release procedure notes should be omitted when minor; when they are important enough to mention, group them into at most one concise bullet.

View file

@ -87,6 +87,6 @@ if (maybeRun("jj", ["root"])) {
run("npm", ["run", "release:check"]);
run("npm", ["ci", "--dry-run"]);
run("npm", ["run", "check"]);
run("npm", ["run", "check:ci"]);
console.log(`release preflight passed for ${packageVersion}`);