From f118944787b332d110bd9ebb4e4221c2cd8cc33c Mon Sep 17 00:00:00 2001 From: murashit Date: Sat, 20 Jun 2026 09:18:17 +0900 Subject: [PATCH] Run API baseline in release preflight --- docs/release.md | 2 +- scripts/release/preflight.mjs | 1 + 2 files changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/release.md b/docs/release.md index 9277b99d..b5f22722 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 the same non-cached `npm run check:ci` validation used by CI 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, API baselines, 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 f72d3bd8..d0fe4ce3 100644 --- a/scripts/release/preflight.mjs +++ b/scripts/release/preflight.mjs @@ -86,6 +86,7 @@ if (maybeRun("jj", ["root"])) { } run("npm", ["run", "release:check"]); +run("npm", ["run", "api:baseline"]); run("npm", ["ci", "--dry-run"]); run("npm", ["run", "check:ci"]);