@thorprovider/storefront 0.13.2 → 0.13.3

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.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@thorprovider/storefront",
3
- "version": "0.13.2",
3
+ "version": "0.13.3",
4
4
  "description": "Deterministic storefront scaffolder and installable OpenCode skill suite for Thor Commerce (Next.js, @thorprovider/blocks, @thorprovider/adapters, Medusa)",
5
5
  "type": "module",
6
6
  "bin": "bin/storefront.js",
@@ -433,13 +433,15 @@ export function verifyRegistryArtifact({
433
433
 
434
434
  /**
435
435
  * `npm publish` returns before every registry edge serves the artifacts. A
436
- * mirror that is still replicating answers 404 for a version that exists, so the
437
- * acceptance gate polls instead of failing a release that published correctly.
438
- * The linear backoff below waits ~3.5 minutes in total: acceptance starts ~30s
439
- * after publishing, and a cold packument edge has been observed to take over a
440
- * minute to serve a brand-new version.
436
+ * mirror that is still replicating answers 404 for a version that exists, so a
437
+ * freshly published pin can look unpublished for a moment.
438
+ *
439
+ * This window stays short on purpose: `create` runs interactively, and a pin
440
+ * that is genuinely missing must fail in seconds, not minutes. The release gate
441
+ * does not rely on it — `scripts/release/wait-for-registry.mjs` holds the run
442
+ * until every pin resolves before acceptance starts.
441
443
  */
442
- export const REGISTRY_RETRY = Object.freeze({ attempts: 7, delayMs: 10_000 })
444
+ export const REGISTRY_RETRY = Object.freeze({ attempts: 2, delayMs: 2000 })
443
445
 
444
446
  const defaultSleep = (ms) => new Promise((done) => setTimeout(done, ms))
445
447