Skip to content

The design language that makes your AI harness better at design.

JavaScript

Point the post-release hint at the site's signed skill pointer (#904)

Paul Bakaus4adabaf2c2bd
diff --git a/CLAUDE.md b/CLAUDE.md
index 817c9fea5..54ce1f7bf 100644
--- a/CLAUDE.md
+++ b/CLAUDE.md
@@ -298,6 +298,7 @@ Workflow for any component:
2. Add a changelog entry to `site/pages/changelog.astro` (see **Website changelog** above for placement and tone). Skill entries use a bare `vX.Y.Z` label; CLI and extension entries use the prefixed forms `CLI vX.Y.Z` and `Extension vX.Y.Z`. The release script extracts notes by matching this label, so the prefix matters.
3. Commit and push to `main`.
4. Run `bun run release:<skill|cli|ext>`. Preview first with `node scripts/release.mjs <component> --dry-run`.
+5. Skill only: `npx impeccable install` / `update` serve the version in impeccable-site's `published-skill.json`, a signed pointer that does not follow the release by itself (site `docs/PUBLISHED-SKILL.md`). On a branch from site main, run `bun run skill:publish-pointer <version>` (it verifies the release signature and checksum), commit the pointer, and merge; the main deploy then serves it. Redeploying without moving the pointer republishes the old version. The release script warns when `impeccable.style/api/version` still lags.
The script refuses to run if: the working tree is dirty, HEAD is ahead of origin, the tag already exists, the matching changelog entry is missing, or (for skill/extension) `bun run build:release` / `bun run build:extension` produces uncommitted changes — meaning the harness output dirs or `extension/detector/` files weren't refreshed before the bump was committed.
diff --git a/scripts/release.mjs b/scripts/release.mjs
index 1b6f6a92a..7c8b47e58 100755
--- a/scripts/release.mjs
+++ b/scripts/release.mjs
@@ -306,10 +306,11 @@ try {
console.log(`\n✓ ${cfg.label} ${version} released as ${tag}`);
-// npx impeccable update serves from impeccable.style, not from this release:
-// the site must be redeployed (its deploy overlays public main first). Warn
-// loudly when the served version lags so a release never silently strands
-// update users on old content again (the 4.0.0 release did exactly that).
+// npx impeccable install/update serve the version named by impeccable-site's
+// published-skill.json, a signed pointer that never follows this release on
+// its own. Redeploying alone republishes the old pointer. Warn loudly when the
+// served version lags so a release never silently strands update users on old
+// content again (the 4.0.0 release did exactly that).
if (component === 'skill' && !dryRun) {
try {
const res = await fetch('https://impeccable.style/api/version');
@@ -318,8 +319,10 @@ if (component === 'skill' && !dryRun) {
console.log(`✓ impeccable.style serves ${served}`);
} else {
console.log(`\n⚠ impeccable.style still serves ${served}, not ${version}.`);
- console.log(' npx impeccable update users get the OLD version until the site redeploys:');
- console.log(' cd ../impeccable-site && bun run deploy');
+ console.log(' npx impeccable install/update serve the OLD version until the site\'s signed pointer moves.');
+ console.log(` In impeccable-site, on a branch from main: bun run skill:publish-pointer ${version}`);
+ console.log(' Commit published-skill.json and merge it to main; the main deploy then serves the new version.');
+ console.log(' If the pointer already names this version, check the site\'s main deploy: wait if it is running, fix it if it failed.');
}
} catch {
console.log('⚠ could not reach impeccable.style/api/version to verify the served bundle');