From 1914e986ed7d480e69c67d524d63d30a4976483b Mon Sep 17 00:00:00 2001 From: murashit Date: Sat, 20 Jun 2026 08:49:34 +0900 Subject: [PATCH] Align release preflight with CI checks --- docs/release.md | 2 +- scripts/release/preflight.mjs | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/release.md b/docs/release.md index 684c8252..9277b99d 100644 --- a/docs/release.md +++ b/docs/release.md @@ -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. diff --git a/scripts/release/preflight.mjs b/scripts/release/preflight.mjs index 5bb63557..f72d3bd8 100644 --- a/scripts/release/preflight.mjs +++ b/scripts/release/preflight.mjs @@ -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}`);