Release script verifies impeccable.style serves the released version

The 4.0.0 release stranded npx-update users on a stale bundle for a
day because the site deploy is a separate step nobody was reminded of.
Skill releases now check /api/version and print the redeploy command
when the served version lags.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
Paul Bakaus
2026-07-22 12:39:32 -07:00
co-authored by Claude Fable 5
parent eda81f0937
commit 087983070b
+20
View File
@@ -211,6 +211,26 @@ 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).
if (component === 'skill' && !dryRun) {
try {
const res = await fetch('https://impeccable.style/api/version');
const served = (await res.json()).skills;
if (served === version) {
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');
}
} catch {
console.log('⚠ could not reach impeccable.style/api/version to verify the served bundle');
}
}
if (cfg.postReleaseHint) {
console.log(`\n→ Next step: ${cfg.postReleaseHint}`);
}