shiply-cli 0.26.0 → 0.26.1

package/dist/framework.js

@@ -8,9 +8,14 @@ const SSG_SIGNATURES = [
     { files: ['mkdocs.yml', 'mkdocs.yaml'], framework: 'MkDocs', outputDir: 'site', buildCommand: 'mkdocs build' },
 ];
 async function detectStaticSiteGenerator(dir) {
+    // Check every signature file in parallel, then pick the first match in the
+    // original priority order — same result as the serial version, faster I/O.
+    const flatFiles = SSG_SIGNATURES.flatMap((sig) => sig.files);
+    const hits = await Promise.all(flatFiles.map((f) => exists(join(dir, f))));
+    let i = 0;
     for (const sig of SSG_SIGNATURES) {
         for (const f of sig.files) {
-            if (await exists(join(dir, f))) {
+            if (hits[i++]) {
                 return { framework: sig.framework, outputDir: sig.outputDir, spa: false, buildCommand: sig.buildCommand };
             }
         }

package/dist/publish.js

@@ -132,8 +132,14 @@ async function uploadAll(dir, targets) {
             const t = targets[next++];
             const body = await readFile(join(dir, t.path));
             const res = await fetchWithRetry(t.url, { method: t.method, headers: t.headers, body }, { label: `upload ${t.path}` });
-            if (!res.ok)
+            if (!res.ok) {
+                if (res.status === 403) {
+                    throw new Error(`upload failed for ${t.path}: HTTP 403 — presigned URLs likely expired ` +
+                        `(they're short-lived). Re-run \`shiply publish\` to mint fresh ones — ` +
+                        `unchanged files are hash-skipped, so the retry is cheap.`);
+                }
                 throw new Error(`upload failed for ${t.path}: HTTP ${res.status}`);
+            }
         }
     };
     await Promise.all(Array.from({ length: Math.min(CONCURRENCY, targets.length) }, worker));

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "shiply-cli",
-  "version": "0.26.0",
+  "version": "0.26.1",
   "description": "Publish static sites to shiply.now from the command line \u00e2\u20ac\u201d instant web hosting for agents.",
   "license": "MIT",
   "type": "module",

package/skill/CHANGELOG.md

@@ -6,6 +6,17 @@ entry here, that capability may be missing from your copy — re-install with
 (This is the agent-facing capability log; the CLI's own release notes live in
 the npm package changelog.)
 
+## 2026-07-08
+
+- **Fix** — re-publishing an unchanged large SSR site (e.g. a 171-file
+  Next.js build) used to take 6+ minutes (serial hash-skip HEAD checks, a
+  serial worker-bundle re-read/re-upload even with no changes, plus a
+  finalize retry after a client-side timeout). Finalize is now: concurrent
+  hash-skip checks, a fingerprinted worker-bundle deploy that's skipped
+  entirely when nothing changed, and an idempotent replay on retry. A
+  zero-change publish now finishes in seconds. No action needed — always
+  re-publish to the same site (slug/claimToken); it's cheap.
+
 ## 2026-07-07
 
 - **Fix** — custom domains attached to SSR/function sites no longer 404: the

package/skill/SKILL.md

@@ -13,7 +13,7 @@ description: "shiply is the production backend for anything an agent builds —
 > the npm package name.
 
 > **Skill freshness check.** Shiply ships new capabilities weekly.
-> **This skill: version 0.25.0, last updated 2026-07-04.**
+> **This skill: version 0.25.0, last updated 2026-07-08.**
 > To see what changed since your copy was written, fetch
 > `https://shiply.now/changelog.md` (date-grouped, newest first) — if it lists
 > capabilities newer than the date above, re-install with
@@ -31,7 +31,14 @@ description: "shiply is the production backend for anything an agent builds —
 **How (quickstart).** `shiply publish ./dir` (CLI) — or POST /api/v1/publish → PUT each file → POST finalize — returns a live URL + claimToken.
 
 **NEVER create a new site to update an existing one. Always re-publish to the
-same site** — otherwise you litter subdomains and lose the user's URL.
+same site** (same slug/claimToken) — otherwise you litter subdomains and lose
+the user's URL.
+
+**Re-publishing the same site is cheap — always prefer it over a new site.**
+Unchanged files are hash-skipped, and an unchanged SSR worker bundle skips
+redeploy entirely (fingerprinted against what's already live). A zero-change
+`shiply publish` on the same site completes in seconds, even for large SSR
+apps — so iterate freely by re-publishing, never by spinning up a fresh site.
 
 This file covers the core path: publish → authorize → update → claim → verify.
 Everything else (databases, domains, SSR, email, functions, client work) lives