@jskit-ai/release 0.1.1 → 0.1.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/package.json +1 -1
  2. package/src/release.mjs +3 -0
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@jskit-ai/release",
3
- "version": "0.1.1",
3
+ "version": "0.1.2",
4
4
  "description": "Selective npm release preparation, publication and dependency pinning for package repositories.",
5
5
  "type": "module",
6
6
  "files": [
package/src/release.mjs CHANGED
@@ -715,6 +715,9 @@ async function installReleasedPins(repoRoot, { attempts = 20, delayMs = Number(p
715
715
  throw new Error(`npm install failed in ${repoRoot}.`);
716
716
  }
717
717
  process.stdout.write(`npm does not serve the new versions yet; retrying in ${Math.round(delayMs / 1000)} s (${attempt}/${attempts})\n`);
718
+ // --prefer-online still reuses a cached package list that predates the
719
+ // release; observed in a real deploy. Drop it so the retry sees the registry.
720
+ spawnSync("npm", ["cache", "clean", "--force"], { cwd: repoRoot, stdio: "ignore" });
718
721
  await new Promise(resolve => setTimeout(resolve, delayMs));
719
722
  }
720
723
  }