fix(ci): make release publish step idempotent

package.json

@@ -13,7 +13,7 @@
     "tarball:audit": "node scripts/tarball-audit/audit.mjs",
     "tree-shake": "node e2e/smoke/tree-shake/check.mjs",
     "changeset": "changeset",
-    "release": "pnpm build && pnpm smoke && pnpm size && pnpm tarball:audit && pnpm tree-shake && cd packages/whisper && npm publish --access public --provenance"
+    "release": "pnpm build && pnpm smoke && pnpm size && pnpm tarball:audit && pnpm tree-shake && node scripts/publish-if-new.mjs"
   },
   "devDependencies": {
     "@biomejs/biome": "2.4.7",

scripts/publish-if-new.mjs

@@ -0,0 +1,52 @@
+#!/usr/bin/env node
+// scripts/publish-if-new.mjs
+// Idempotent npm publish: skip if the current version is already on the registry.
+//
+// Why: release.yml runs on every push to main. changesets/action only opens a
+// "Version Packages" PR when there are pending changesets — on pushes that
+// merge non-changeset PRs (e.g. CI tweaks), the action falls through to the
+// publish step. Without this guard, `npm publish` errors out with
+// "You cannot publish over the previously published versions" and fails the
+// release job for every infra-only merge.
+//
+// Direct `npm publish` (rather than `changeset publish`) is intentional —
+// the project uses npm 11.5.1+ trusted publishing with provenance, which
+// `changeset publish` doesn't pass through cleanly.
+
+import { execFileSync, spawnSync } from 'node:child_process';
+import { readFileSync } from 'node:fs';
+import { dirname, resolve } from 'node:path';
+import { fileURLToPath } from 'node:url';
+
+const __dirname = dirname(fileURLToPath(import.meta.url));
+const pkgPath = resolve(__dirname, '../packages/whisper/package.json');
+const pkg = JSON.parse(readFileSync(pkgPath, 'utf8'));
+const { name, version } = pkg;
+
+let published = '';
+try {
+  published = execFileSync('npm', ['view', `${name}@${version}`, 'version'], {
+    encoding: 'utf8',
+    stdio: ['ignore', 'pipe', 'pipe'],
+  }).trim();
+} catch (err) {
+  // E404 from `npm view` means the version is not published — that's the
+  // happy "publish me" path. Anything else is a real registry/network error.
+  const stderr = err.stderr?.toString() ?? '';
+  if (!stderr.includes('E404') && !stderr.includes('code E404')) {
+    process.stderr.write(stderr);
+    process.exit(err.status ?? 1);
+  }
+}
+
+if (published === version) {
+  console.log(`publish-if-new: ${name}@${version} already on registry — skipping publish.`);
+  process.exit(0);
+}
+
+console.log(`publish-if-new: publishing ${name}@${version}...`);
+const result = spawnSync('npm', ['publish', '--access', 'public', '--provenance'], {
+  cwd: resolve(__dirname, '../packages/whisper'),
+  stdio: 'inherit',
+});
+process.exit(result.status ?? 1);