Skip to content

YC (S26) | Open Computer History | Continuously record your company computer work, map your workflows, help you find work worth automating, and power your agents' context

docs(release): document manual exact-SHA dispatch

Louis Beaumontc2921a8eeb47
diff --git a/.claude/skills/release/SKILL.md b/.claude/skills/release/SKILL.md
index 05e91149f..2dbab3c0d 100644
--- a/.claude/skills/release/SKILL.md
+++ b/.claude/skills/release/SKILL.md
@@ -83,14 +83,22 @@ Cargo.toml leaves the other locks stale and breaks `cargo test --locked` on main
Commit the regenerated locks together with the bump. `style.yml` runs
`./scripts/regenerate-locks.sh --check` on every push and fails if any lock is stale.
-### 4. Commit & Push (Triggers Release)
+### 4. Commit, Push, and Dispatch Exact SHA
```bash
git add -A && git commit -m "Bump app to vX.Y.Z" && git pull --rebase && git push
+
+BUMP_SHA=$(git rev-parse HEAD)
+gh workflow run release-app.yml \
+ --ref main \
+ -f commit_hash="$BUMP_SHA" \
+ -f version="X.Y.Z" \
+ -f needs_testing=false \
+ -f force_github_runners=false
```
-Pushing a commit whose message starts with `Bump app` or `release-app` to `main` triggers `release-app.yml` automatically (`check_commit` job gates on the prefix). The workflow only builds, signs, notarizes, and uploads immutable versioned artifacts. It does not publish updater pointers or create the public GitHub release.
+`release-app.yml` is currently `workflow_dispatch` only. A bump push does not start it. Dispatch it once with the exact pushed commit and version inputs; its workflow builds, signs, notarizes, and uploads immutable versioned artifacts. It does not publish updater pointers or create the public GitHub release.
-**Do NOT also run `gh workflow run release-app.yml`** — it fires a second `workflow_dispatch` run on the same SHA, doubling the build. The push handles it.
+Before dispatching, verify the remote `main` SHA still matches `BUMP_SHA`. After dispatching, read the run back and require its `headSha` to match. Never dispatch a second app run for the same version unless the first run failed and the retry is intentional.
Enterprise is separate and manual. After the bump commit is on `main`, dispatch `release-enterprise.yml` once and verify that its run is pinned to the bump commit before treating Enterprise artifacts as prepared.
@@ -118,11 +126,15 @@ After testing and artifact verification, stop at the authenticated releases cont
# 2. Regenerate every tracked Cargo.lock (skipping this breaks `cargo test --locked` in CI)
./scripts/regenerate-locks.sh
-# 3. Commit and push — the "Bump app" prefix triggers release-app.yml automatically
+# 3. Commit and push the version bump
git add -A && git commit -m "Bump app to vX.Y.Z" && git push
-# 4. Monitor
-sleep 5 && gh run list --workflow=release-app.yml --limit=1
+# 4. Dispatch the exact pushed commit once, then monitor
+BUMP_SHA=$(git rev-parse HEAD)
+gh workflow run release-app.yml --ref main \
+ -f commit_hash="$BUMP_SHA" -f version="X.Y.Z" \
+ -f needs_testing=false -f force_github_runners=false
+gh run list --workflow=release-app.yml --limit=1
```
## Build Status Format
@@ -173,10 +185,10 @@ The CI copies `tauri.prod.conf.json` to `tauri.conf.json` before building. If ar
CI automatically uses prod config for releases by copying it before build.
### Trigger & Publication Behavior
-- Commit prefix `Bump app` or `release-app` pushed to main → consumer artifact build/upload
+- `release-app.yml` is `workflow_dispatch` only → consumer artifact build/upload from the explicit commit/version inputs
- `release-enterprise.yml` is `workflow_dispatch` only → Enterprise artifact build/upload
- Public consumer and Enterprise publication remains a human-only admin-dashboard action after artifact verification
-- Manual `release-app.yml` dispatch is redundant with the bump push; avoid running both
+- A bump push alone starts neither release workflow; dispatch each exactly once and verify both run SHAs
## Notes