Skip to content

an open-source alternative to the dots, bots and muses of the world, run an office of claude code/codex like agents on your laptop, sandboxes or anywhere, uses your existing subscriptions

docs: retarget the updater checklist to the rc rehearsal, link it from RELEASE.md

Chaitanya Giri980bb1a1417b
diff --git a/RELEASE-CHECKLIST.md b/RELEASE-CHECKLIST.md
index 60554e40..55e744d3 100644
--- a/RELEASE-CHECKLIST.md
+++ b/RELEASE-CHECKLIST.md
@@ -6,25 +6,46 @@ build after it lands, not by the build itself. This checklist is how a release
runner confirms it, because the paths that matter most are the ones a clean,
successful release never touches.
-## The proving hop
+## The proving hop (rehearse on prereleases, before the real release)
`0.4.6` is delivered by `0.4.5`'s updater, so `0.4.6` arriving proves the OLD
-code worked. Only a hop AFTER `0.4.6` runs the code we wrote. Cut a throwaway
-`0.4.7` whose only job is to be found and installed.
+code worked. Only a hop that STARTS on our new code proves it. So rehearse on
+prereleases first: publish `0.4.6-rc.1`, then a no-op `0.4.7-rc.1`, and drive
+the hop `0.4.6-rc.1` -> `0.4.7-rc.1` on a test machine BEFORE the real `0.4.6`
+exists. Same evidence, earlier, with any failure landing on a throwaway.
-**Release gate (hard): `0.4.7` must be a COMPLETE signed, notarized, stapled run
-of the real pipeline, not a `git tag` and not a version bump.** macOS updates
+Why it is safe: a `-rc.1` tag publishes as a GitHub pre-release (release.yml,
+`prerelease: contains(ref_name, '-')`), and electron-updater only offers a
+pre-release to a client whose OWN version is a pre-release (allowPrerelease
+defaults to that, verified in 6.8.9). So a stable `0.4.5` client sees neither
+rc, on the native path or the notify-only fallback. Only a machine already on
+`0.4.6-rc.1` sees `0.4.7-rc.1`.
+
+Two things to hold: a tester must MANUALLY install `0.4.6-rc.1` first (a `0.4.5`
+machine sees nothing, which is the point); and a machine left on `0.4.7-rc.1`
+stays AHEAD of the real `0.4.6` (`0.4.7-rc.1 > 0.4.6` and we do not allow
+downgrade), so reset rehearsal machines by reinstalling manually afterward. A
+`0.4.6-rc.1` machine that does nothing self-heals to the real `0.4.6` when it
+ships, because a release outranks its own pre-release.
+
+If the rehearsal passes, the real `0.4.6` is that SAME tree with only
+`package.json`'s version bumped from `0.4.6-rc.1` to `0.4.6` (the build reads
+the version from package.json, not the tag), nothing else. Any CODE change
+between the rehearsal and the release means re-rehearse.
+
+**Release gate (hard): each rc (and the real release) must be a COMPLETE signed,
+notarized, stapled run of the real pipeline, not a `git tag` and not a version bump.** macOS updates
through Squirrel.Mac, which needs `mac-universal.zip` + its `.blockmap` +
`latest-mac.yml` (whose `path:` must point at the zip, not the dmg). A release
missing those silently falls back to manual and proves nothing.
## What a clean 0.4.7 proves on its own (the happy path)
-Install `0.4.6`, publish a complete `0.4.7`, then watch one client:
+Install `0.4.6-rc.1`, publish a complete `0.4.7-rc.1`, then watch that client:
- [ ] the badge moves check -> available -> downloading -> downloaded on its own
- [ ] at `downloaded` the badge's primary action is **restart**, not a manual download
-- [ ] clicking it quits, installs `0.4.7`, and relaunches into the new version
+- [ ] clicking it quits, installs `0.4.7-rc.1`, and relaunches into the new version
- [ ] after relaunch the badge shows the "just updated" state
## What a clean release CANNOT reach (inject these by hand)
diff --git a/RELEASE.md b/RELEASE.md
index 6f209c45..226c802f 100644
--- a/RELEASE.md
+++ b/RELEASE.md
@@ -1,3 +1,4 @@
+<!-- RELEASE RUNNER, REQUIRED BEFORE YOU TAG: run RELEASE-CHECKLIST.md. Rehearse the updater on 0.4.6-rc.1 -> 0.4.7-rc.1 prereleases and pass the fault-injection checks BEFORE tagging the real release. This comment is not rendered in the published notes. -->
# Munder Difflin v0.4.5
**A local hive of Claude Code, Antigravity, Codex, Gemini, Cursor, Grok & Copilot agents that run themselves.**