archilyzer

commit 39fa1d9fb9c629411f4eea0bc03e88921b57b61d
parent cd8c0d76f58321f3522c851c2e3425be2ab20f2c
Author: I Mean I'm Just Saying <imeanimjustsaying@kiwifarms.st>
Date:   Mon, 28 Sep 2026 02:20:06 -0400

sites: the Cut release form revalidates when the heading was written but the commit failed

The deferred half of release 10 review L3 (O3 item 4), after O4's merge:
cutReleaseForWorkspace returns written: true exactly then, and the pages
that render the changelog are stale all the same. The error sentence
already says the file changed.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

Diffstat:
M
editor/app/sites/lib/cutReleaseAction.ts
 | 
8
+++++++-

1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/editor/app/sites/lib/cutReleaseAction.ts b/editor/app/sites/lib/cutReleaseAction.ts
@@ -38,7 +38,13 @@ export async function cutReleaseAction(
     version,
     commit: shouldCommit,
   });
-  if (!result.ok) return { ok: false, error: result.error };
+  if (!result.ok) {
+    // The heading was written and only the commit after it failed (release 11
+    // slice O3, release 10 review L3): the pages that render this changelog
+    // are stale all the same. The error already says the file changed.
+    if (result.written) revalidateAfterReleaseCut();
+    return { ok: false, error: result.error };
+  }
   revalidateAfterReleaseCut();
   return { ok: true, version: result.version, committed: result.committed };
 }