release
Skill11 starsChanged 2 days agoMITView on GitHub
Cut a new Claudesk release — bump the version, clean-build the .dmg + updater artifacts (.app.tar.gz + .sig + signed latest.json), publish a GitHub release, and bump the Homebrew tap cask. MANUAL-ONLY; invoke by hand when the operator says "cut a release" / "ship a release" / "/release". NEVER auto-invoked by feature-ship or product-finalize.
- Deletes or force-pushes
- Installs packages
- Commits and pushes
193 other projects use a version of this.
Adopted by
Most recently taken up by
- yicheng47/runnertheir own version, first seen Nov 13, 2026
- eugene1g/agent-safehousetheir own version, first seen Nov 12, 2026
- BlockRunAI/ClawRoutertheir own version, first seen Nov 11, 2026
- cubeplexai/cubeplextheir own version, first seen Nov 10, 2026
- bex-co/bextheir own version, first seen Nov 10, 2026
- Yeachan-Heo/oh-my-claudecodetheir own version, first seen Nov 9, 2026
Used with
Projects with it also use create-agent-adapter, changelog-style and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
MicrosoftSkillcreate-agent-adapter
Technical guide for creating a new Paperclip agent adapter. Use when building a new adapter package, adding support for a new AI coding tool (e.g. a new CLI agent, API-based agent, or custom process), or when modifying the adapter system. Covers the required interfaces, module structure, registration points, and conventions derived from the existing claude-local and codex-local adapters.
Also in 5 projects that use this
GrinvSkillchangelog-style
Turn a commit range into CHANGELOG.md entries following common-changelog style. Use when finishing a PR or cutting a release, to write/fix the [Unreleased] section's entries — moving [Unreleased] under a new dated version heading is a separate, automated step (see the release skill / scripts/sync-version.ts), not this skill's job.
Also in 4 projects that use this
GrinvSkilldocs-consistency-check
Check README/manifest.json/server.json/CHANGELOG.md/AGENTS.md and docs/*.md for drift against the actual registered tools and source. Use after adding, renaming, or removing a tool, or as part of a live-audit pass.
Also in 4 projects that use this
Microsoft AzureSkillcomponent-release
Prepares a verifiable Agent Landing Zone UI release. Use for release branches, VERSION, changelog entries, tags, release notes, and compatibility evidence; never publish without explicit human approval.
Also in 4 projects that use this
Microsoft AzureSkilldocumentation-consistency
Keeps AI Landing Zone contributor, user, and operator documentation aligned with shipped Bicep behavior. Use for parameters, defaults, outputs, topology, deployment flow, operations, or releases.
Also in 8 projects that use this
rivet-devSkilllaunch-graphics
Generate agentOS marketing/launch graphics (launch & social heroes, code-snippet cards) from the committed generators in docs-internal/graphics. Use when asked to make, update, or render an agentOS launch image, social image, "agentOS Apps" graphic, or technical code-snippet image.
Also in 3 projects that use this
- +3 more from Grinv
Other versions193 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 193
- paperclipai/paperclip★ 114ksame name
- modelcontextprotocol/servers★ 92ksame name
- remotion-dev/remotion★ 73ksame name
- traefik/traefik★ 66ksame name
- usememos/memos★ 64ksame name
- tw93/Pake★ 64ksame name
- amruthpillai/reactive-resume★ 46ksame name
- reactive-resume/reactive-resume★ 46ksame name
- AmruthPillai/Reactive-Resume★ 45ksame name
- Yeachan-Heo/oh-my-claudecode★ 41ksame name
183 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository2 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- clear-build-cacheSkill
The file
We split this skill into the rules it gives an agent
11 rules. 0 are common, 3 are distinctive, and 8 are very specific to this project.
0
Common
Most of the 183 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
8
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 35
If you find yourself about to call this skill from inside another skill's chain, stop: that's the failure mode this constraint exists to …
- Very specific: line 73
If missing (new machine / lost key): STOP.
- Very specific: line 130
Run from the project root (/Users/stayman/Personal/projects/claudesk).
- Very specific: line 246
If they are absent, APPLE_SIGNING_IDENTITY was not exported into the build's shell.
- Very specific: line 366
Draft the release notes from the CHANGELOG: Read CHANGELOG.md and collect the entries added since the previous release tag (git tag …
- Distinctive: line 432
Wait for explicit approval (and apply any edits the operator gives).
- Distinctive: line 491
If audit or style fails, fix the cask and re-validate before the gate.
- Very specific: line 504
Clean up the transient manifest, then report: Remove the repo-root latest.json (it's already uploaded to the release.
- Very specific: line 519
Homebrew 6.x removed
--no-quarantine: Do NOT put brew install --cask --no-quarantine claudesk in release notes or the README — it errors … - Very specific: line 529
Cask
verified:param: Don't add verified: to the url when the url domain == homepage domain (both github.com) — brew audit rejects it as … - Very specific: line 533
Always cp your edited claudesk.rb into $(brew --repository)/Library/Taps/staymanhou/homebrew-claudesk/Casks/ before auditing, or push first …
“Common” is measured: kept by at least 6 in 10 of the 183 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Release Claudesk
Drives a full Claudesk release end-to-end: bump the version, do a clean production
build, tag the commit, publish a GitHub release with four assets — the .dmg
(first-install / Homebrew) plus the three in-app-updater artifacts (Claudesk.app.tar.gz,
its minisign .sig, and the signed latest.json manifest) — and update the Homebrew
tap cask (StaymanHou/homebrew-claudesk) so brew install --cask claudesk picks up
the new version. The updater artifacts are what a running Claudesk downloads to
self-update (M10); the .dmg/cask path is unchanged.
The flow pauses at two human gates — before publishing the GitHub release, and before pushing the tap cask — because both are irreversible outward-facing actions.
⚠️ MANUAL-ONLY — do not wire into any workflow
This skill is invoked ONLY by the operator, by hand (they say "cut a release",
"ship a release", or /release). It is deliberately a standalone skill with no
transition wiring into the feature or product state machines.
feature-shipMUST NOT invoke it. Shipping a feature is a git push, not a product release.product-finalizeMUST NOT invoke it. Closing a milestone/WBS cycle is a docs-and-archive operation, not a product release.- A release is an outward-facing publish (cuts a public GitHub release + a binary friends will install). It happens on the operator's explicit say-so and never as a side effect of any close skill. If you are an orchestrator driving a workflow and you reach a "ship"/"finalize"/"close" step, do not reach for this skill — releasing is out of band.
If you find yourself about to call this skill from inside another skill's chain, stop: that's the failure mode this constraint exists to prevent.
Preconditions
- Working tree clean, on
main. Uncommitted changes must be dealt with before starting (this skill will add a version-bump commit of its own). ghinstalled and authenticated (gh auth status). If missing:brew install gh && gh auth login(the auth is interactive — the operator runs it).- Apple Silicon host — the build produces an
aarch64.dmg. Tap repo present at
homebrew-claudesk/nested inside this project (its own independent git repo; gitignored by the canonical claudesk repo). If absent, clone it there:gh repo clone StaymanHou/homebrew-claudesk homebrew-claudesk. Confirm its remote is SSH —git -C homebrew-claudesk remote get-url originshould printgit@github.com:StaymanHou/homebrew-claudesk.git. If a fresh clone came down over HTTPS, switch it:git -C homebrew-claudesk remote set-url origin git@github.com:StaymanHou/homebrew-claudesk.gitUpdater signing key present at
~/.claudesk-release-keys/(created M10 WP5):claudesk-release.key— the minisign private key (chmod 600, NEVER committed).claudesk-release.key.pass— its password (chmod 600, a random string; NEVER committed).claudesk-release.key.pub— the public key, key ID774E2E8429FDF78A. Its base64 form is baked intosrc-tauri/tauri.conf.json→plugins.updater.pubkey— the trust anchor every published update is verified against. Do NOT change the config pubkey unless you are deliberately rotating the key (a key rotation strands users on the old key until theybrew upgrade/re-download — see "first updatable release is the FLOOR" below).
Confirm the key files are present before starting; if this machine doesn't have them, the build's sign step (step 3) cannot produce the
.sigand the release cannot ship updater artifacts:ls -la ~/.claudesk-release-keys/claudesk-release.key ~/.claudesk-release-keys/claudesk-release.key.passIf missing (new machine / lost key): STOP. Either restore the key from your secret backup, or — if genuinely lost — mint a new one (
pnpm exec tauri signer generate -w ~/.claudesk-release-keys/claudesk-release.key), swap the new.pubintotauri.conf.json, and accept that this becomes a key rotation.Apple Developer ID signing identity + notarization credential present (M14 WP2, 2026-09-18). Claudesk is signed and notarized as of v0.5.2 — these are hard preconditions, not optional extras.
security find-identity -v -p codesigning | grep "Developer ID Application" xcrun notarytool history --keychain-profile "claudesk-notary" >/dev/null && echo "notary OK"⚠️ Both must succeed before you start. The first must print exactly one
Developer ID Application: …line; the second is a real authenticated round-trip to Apple (it prints submission history, or "No submission history" on a fresh account — both are success; an auth failure is not).⚠️
security find-identity -vreporting0 valid identitieswhile the cert IS in Keychain Access means Apple's G2 intermediate is missing, not that the cert is bad. Symptom chain: red "certificate is not trusted" in Keychain Access →codesignfails withunable to build chain to self-signed root→errSecInternalComponent. Fix (idempotent, no sudo, login keychain only):curl -fsSL -o /tmp/DeveloperIDG2CA.cer https://www.apple.com/certificateauthority/DeveloperIDG2CA.cer security import /tmp/DeveloperIDG2CA.cer -k ~/Library/Keychains/login.keychain-db⚠️ Do NOT validate the identity with
security verify-cert— it uses a different trust evaluation and returns "verification successful" in exactly the state wherecodesigncannot build the chain. A false all-clear. Test-sign a throwaway binary instead, or just trustfind-identity -v.
Inputs
- Version — e.g.
0.1.1. Ask the operator if not given. Throughout these steps, letVERbe the version (no leadingv); the git tag isvVER.- In prose and in the version-bump edits (step 2),
VER/vVERare textual placeholders you substitute by hand (Claudesk_VER_aarch64.dmg→Claudesk_0.2.6_aarch64.dmg). In the shell blocks from step 3 onward (signing export,
latest.jsongen,gh release create, the endpoint check),$VER/${VER}are used as a live shell variable. Export it once at the top of your release shell before running those blocks so every$VERexpands correctly (and so the same shell holds it across steps):export VER=0.2.6 # ← the version you're cutting, no leading v(Or derive it:
export VER="$(jq -r .version src-tauri/tauri.conf.json)"after the step-2 bump commit, so it matches the source of truth.) The step-3+ blocks assume$VERis set; an unset$VERempty-expands (Claudesk__aarch64.dmg, a versionlessurl, an empty manifestversion) — set it first.
- In prose and in the version-bump edits (step 2),
Steps
Run from the project root (/Users/stayman/Personal/projects/claudesk).
Check preconditions (above). Confirm
gh auth statusis OK, the working tree is clean, and the tap repo is present with an SSH remote. STOP and tell the operator if any fails.Advisory, never blocking: the
notification_typevocabulary check. List what CC has actually sent:sqlite3 -readonly "$HOME/Library/Application Support/com.claudesk.app/time-analytics.sqlite" \ "SELECT json_extract(meta,'\$.notification_type') AS t, count(*) FROM events WHERE t IS NOT NULL GROUP BY t ORDER BY 2 DESC;"Compare it with the two lists in
status_broadcaster/mod.rs(INPUT_NEEDED_NOTIFICATION_TYPESandINFORMATIONAL_NOTIFICATION_TYPES). Any type in neither list falls back to AwaitingInput, which is right for an input-needed type and wrong for a completion one (agent_completedlit the dot blue that way). For a new type, file a SURFACE and tell the operator, but do not hold the release. The fallback itself must NOT be inverted.Bump the version. Edit both:
src-tauri/tauri.conf.json→versionsrc-tauri/Cargo.toml→[package] version
Then refresh
Cargo.lock(so itsclaudeskentry matches the new version), commit, and push:(cd src-tauri && cargo update -p claudesk) # rewrites the claudesk version in Cargo.lock; no network ./node_modules/.bin/prettier --write src-tauri/tauri.conf.json ./node_modules/.bin/prettier --check src-tauri/tauri.conf.json # parse sanity only: right after --write it cannot catch a reflow git add src-tauri/tauri.conf.json src-tauri/Cargo.toml src-tauri/Cargo.lock git commit -m "Release vVER" git push origin main(
cargo update -p claudeskjust re-resolves the local package's own entry in the lockfile to the newCargo.tomlversion — it does not bump dependencies. If for any reasonCargo.lockstill shows the old version, the clean build in step 3 will rewrite it; re-stage and amend if so. The release must point at a pushed commit.)⚠️ The Prettier pass is not optional. Editing the version with a JSON tool (or a re-serializing editor) reflows
tauri.conf.json— v0.6.0's release commit expanded the one-lineresourcesarray, which failedformat:checkand turnedpnpm verify:autored onmainfor every later WP. Only the version line should change in this file's diff.Export the updater-signing env vars, then clean build. The build's integrated sign step produces the updater artifact and its
.sig— but ONLY if the private key is supplied as a string inTAURI_SIGNING_PRIVATE_KEY(see the "Updater signing" gotcha below —..._PATHdoes NOT work for the build auto-sign path and ships an unsigned.tar.gz). Export both env vars in the same shell as the build:export TAURI_SIGNING_PRIVATE_KEY="$(cat ~/.claudesk-release-keys/claudesk-release.key)" export TAURI_SIGNING_PRIVATE_KEY_PASSWORD="$(cat ~/.claudesk-release-keys/claudesk-release.key.pass)" export APPLE_SIGNING_IDENTITY="Developer ID Application: Yuechen Hou (C8RJH77B47)"(The private key + its password live in
~/.claudesk-release-keys/— see "Updater signing key" in Preconditions. Both are read as file CONTENTS via$(cat …); never echo either value, never paste it into a committed file.)⚠️
APPLE_SIGNING_IDENTITYis deliberately an env var, nottauri.conf.json. The tracked config carries onlybundle.macOS.hardenedRuntime+.entitlements, so the repo stays machine-independent andpnpm tauri:devkeeps working for anyone without the cert. SettingsigningIdentityin the config would break a contributor's dev build.⚠️ Notarization is a SEPARATE step (5c), deliberately not wired into the build. Tauri can notarize during
tauri buildifAPPLE_ID+APPLE_PASSWORD+APPLE_TEAM_IDare exported — but when they are absent it printsWarn skipping app notarizationand STILL EXITS 0. That failure mode ships an un-notarized build that looks like a successful release. This skill therefore notarizes explicitly in step 5c and verifies in step 5d, where a miss is loud.Then a full cold rebuild guarantees no stale-cache artifact ships:
(cd src-tauri && cargo clean) pnpm tauri buildThis is a long cold build (multi-minute — likely 3–8 min). Pass an explicit Bash
timeout(consultruntimes.mdfor the recordedpnpm tauri buildtime; if absent, use 600000 ms — the Bash max — and record the observed time toruntimes.mdafterward). Three artifacts land:src-tauri/target/release/bundle/dmg/Claudesk_VER_aarch64.dmg(first-install / Homebrew)src-tauri/target/release/bundle/macos/Claudesk.app.tar.gz(updater payload)src-tauri/target/release/bundle/macos/Claudesk.app.tar.gz.sig(minisign signature)
Confirm all three exist — and specifically that the
.sigis present:ls -la src-tauri/target/release/bundle/dmg/Claudesk_${VER}_aarch64.dmg ls -la src-tauri/target/release/bundle/macos/Claudesk.app.tar.gz \ src-tauri/target/release/bundle/macos/Claudesk.app.tar.gz.sig⚠️ If
Claudesk.app.tar.gz.sigis MISSING, the build did not sign (the env var wasn't exported as a string, or the password was wrong). STOP — do not publish an unsigned updater artifact (the app would reject the update at verify time). Re-exportTAURI_SIGNING_PRIVATE_KEY(contents, not path) + the password and rebuild.Confirm the build was Apple-signed (this is separate from minisign):
codesign -dv --verbose=2 src-tauri/target/release/bundle/macos/Claudesk.app 2>&1 \ | grep -E "flags=|Authority=Developer ID Application"⚠️ Expect
flags=0x10000(runtime)and anAuthority=Developer ID Application: …line. ⚠️ Do NOT check$?here —codesignexits 0 even when signing failed, leaving the previous signature in place. TheAuthority=lines are the evidence. If they are absent,APPLE_SIGNING_IDENTITYwas not exported into the build's shell.
3b. Notarize the .dmg and staple both artifacts. ⚠️ This step is why the release
no longer needs an xattr workaround — spctl only reports
source=Notarized Developer ID once the ticket is stapled.
xcrun notarytool submit src-tauri/target/release/bundle/dmg/Claudesk_${VER}_aarch64.dmg \
--keychain-profile "claudesk-notary" --waitThis uploads to Apple and blocks until a verdict (typically 1–5 min; it has taken
longer). Pass an explicit Bash timeout of 600000 ms. The final line must read
status: Accepted.
⚠️ If the status is Invalid, get the reason before changing anything —
xcrun notarytool log <submission-id> --keychain-profile "claudesk-notary". The
usual causes are a missing hardened runtime or an unsigned nested binary, both of
which are build-config problems, not notarization problems.
Then staple the ticket to both artifacts:
xcrun stapler staple src-tauri/target/release/bundle/dmg/Claudesk_${VER}_aarch64.dmg
xcrun stapler staple src-tauri/target/release/bundle/macos/Claudesk.app3c. ⚠️ RE-TAR AND RE-SIGN THE UPDATER PAYLOAD — do not skip this. Tauri builds
Claudesk.app.tar.gz during the build, i.e. before step 3b stapled the
.app. The tarball on disk therefore contains an unstapled app, and its .sig
was computed over those stale bytes. Shipping it means every self-updating user
receives an app whose Gatekeeper check must go online to fetch the ticket — which
fails offline and re-introduces exactly the first-launch friction this milestone
deleted.
(cd src-tauri/target/release/bundle/macos && \
COPYFILE_DISABLE=1 tar --no-mac-metadata --no-xattrs -czf Claudesk.app.tar.gz Claudesk.app)
./node_modules/.bin/tauri signer sign \
-k "$TAURI_SIGNING_PRIVATE_KEY" -p "$TAURI_SIGNING_PRIVATE_KEY_PASSWORD" \
src-tauri/target/release/bundle/macos/Claudesk.app.tar.gz⚠️ The --no-mac-metadata --no-xattrs flags (and COPYFILE_DISABLE=1) are load-bearing:
without them v0.7.1 shipped a payload that NO self-updating user could install. If the
bundle root carries any extended attribute, macOS tar writes an AppleDouble entry
._Claudesk.app as the archive's FIRST member. For example, macOS adds com.apple.macl as
soon as the bundle's binary is executed, and a smoke-run of Contents/MacOS/claudesk … did
exactly that. tauri-plugin-updater strips the first path component of every entry
(path().iter().skip(1)), so that entry unpacks onto the extraction dir itself. The result
is install: failed to unpack ._Claudesk.app into …/tauri_updated_appXXXX/, and the update
aborts. macOS tar -t HIDES ._ entries (it folds them back into xattrs), so a normal
listing looks clean; check 4 below lists the RAW members instead. The stapled ticket is
not an xattr (it lives in Contents/CodeResources), so dropping xattrs loses nothing.
A no-xattr payload was measured 2026-09-29 as source=Notarized Developer ID.
⚠️ Order is load-bearing: staple → re-tar → re-sign. Re-tarring invalidates the
original .sig (different bytes), so the re-sign is mandatory, not optional. Verify
the payload actually carries the ticket:
rm -rf /tmp/tarcheck && mkdir -p /tmp/tarcheck
tar -xzf src-tauri/target/release/bundle/macos/Claudesk.app.tar.gz -C /tmp/tarcheck
xcrun stapler validate /tmp/tarcheck/Claudesk.app && rm -rf /tmp/tarcheck⚠️ does not have a ticket stapled to it means you skipped or mis-ordered 3c.
3d. Verify the release artifacts — all four checks, all required. ⚠️ Run this
LAST, after every step that writes or moves a bundle. A notarization ticket is
carried in extended attributes, and several ordinary file operations silently drop
them (see the cp -R warning below), so a verification that runs before the final
file movement proves nothing about what ships.
# 1-2. the .app: signed, and NOTARIZED (not merely signed)
codesign --verify --deep --strict --verbose=2 src-tauri/target/release/bundle/macos/Claudesk.app
spctl -a -t exec -vvv src-tauri/target/release/bundle/macos/Claudesk.app
# 3. the .dmg (first-install / Homebrew path)
xcrun stapler validate src-tauri/target/release/bundle/dmg/Claudesk_${VER}_aarch64.dmg
# 4. ⚠️ THE UPDATER PAYLOAD — what self-updating users actually receive.
# Checks 1-3 all pass while this one fails if 3c was skipped or mis-ordered.
rm -rf /tmp/payloadcheck && mkdir -p /tmp/payloadcheck
tar -xzf src-tauri/target/release/bundle/macos/Claudesk.app.tar.gz -C /tmp/payloadcheck
xcrun stapler validate /tmp/payloadcheck/Claudesk.app
spctl -a -t exec -vvv /tmp/payloadcheck/Claudesk.app
rm -rf /tmp/payloadcheck
# 4b. ⚠️ the RAW member list (macOS `tar -t` hides AppleDouble `._` entries — see 3c).
# Every member must sit under `Claudesk.app/`; a top-level non-dir entry breaks install.
python3 -c 'import tarfile,sys; ms=tarfile.open(sys.argv[1]).getmembers(); bad=[m.name for m in ms if m.name.split("/")[-1].startswith("._") or (len(m.name.strip("/").split("/"))<2 and not m.isdir())]; print(len(ms), "members, first", repr(ms[0].name), "BAD:" if bad else "OK", bad or ""); sys.exit(1 if bad else 0)' \
src-tauri/target/release/bundle/macos/Claudesk.app.tar.gz⚠️ codesign alone does not prove notarization. The decisive line is spctl
printing source=Notarized Developer ID — if it says source=Developer ID or
source=Unnotarized Developer ID, the ticket is missing and users will hit
Gatekeeper. STOP and redo 3b–3c rather than publishing.
⚠️ Check 4 is the one that catches a broken updater path. The .app and .dmg
can both verify clean while the tarball carries an unstapled bundle — that is exactly
the 3c failure mode, and it is invisible to checks 1–3 because they read a different
artifact. The tarball is the only one a self-updating user ever sees.
⚠️ cp -R STRIPS THE NOTARIZATION TICKET. Verified 2026-09-18: copying a stapled
.app with cp -R yields spctl → rejected, source=Unnotarized Developer ID. Extended
attributes do not survive a plain copy. If you ever need to move a stapled bundle, use
ditto (which preserves xattrs) or re-staple afterwards — and re-run this step. The
updater's own install path extracts via tar::Archive::unpack + rename. ⚠️ Corrected
2026-09-29: this used to claim "tar does restore xattrs, which is why 3c's re-tar
works". That was the wrong reason. The payload stays notarized because a bundle's stapled
ticket is in Contents/CodeResources, a regular file. And the tar crate does NOT
interpret AppleDouble ._ entries: it unpacks them as literal files, which is what broke
v0.7.1 (see 3c).
Compute the SHA-256 (the cask needs it; keep the hash):
shasum -a 256 src-tauri/target/release/bundle/dmg/Claudesk_${VER}_aarch64.dmgDraft the release notes from the CHANGELOG. Read
CHANGELOG.mdand collect the entries added since the previous release tag (git tag --sort=-v:refname→ the tag beforevVER;git log <prevtag>..HEADto see what landed). Draft a short release-notes body summarizing those entries, and always append the standard install block:Install via the tap: `brew tap StaymanHou/claudesk && brew trust --cask StaymanHou/claudesk/claudesk && brew install --cask claudesk`⚠️ The unsigned-build caveat is GONE as of v0.5.2 (M14 WP2). Builds are Developer-ID signed and Apple-notarized, so Gatekeeper admits them unaided. Do not re-add an
xattr -dr com.apple.quarantineline to release notes — it would instruct users to work around a problem that no longer exists, and it teaches a habit that weakens Gatekeeper for unrelated software.
5b. Generate the updater manifest latest.json. This is the file the running app
polls (plugins.updater.endpoints in tauri.conf.json →
https://github.com/StaymanHou/Claudesk/releases/latest/download/latest.json). Compose
it from data already in hand — VER, the .sig contents, and the eventual asset URL:
SIG="$(cat src-tauri/target/release/bundle/macos/Claudesk.app.tar.gz.sig)"
PUB_DATE="$(date -u +%Y-%m-%dT%H:%M:%SZ)"
NOTES="<one-line summary — reuse the release-notes headline from step 5>" # ← SUBSTITUTE before running
jq -n \
--arg version "$VER" \
--arg notes "$NOTES" \
--arg pub_date "$PUB_DATE" \
--arg sig "$SIG" \
--arg url "https://github.com/StaymanHou/Claudesk/releases/download/v${VER}/Claudesk.app.tar.gz" \
'{version:$version, notes:$notes, pub_date:$pub_date,
platforms:{"darwin-aarch64":{signature:$sig, url:$url}}}' \
> latest.json⚠️ Substitute the NOTES= placeholder with the real headline before running —
unlike signature/url, notes has no downstream sanity-check, so an un-substituted
<one-line summary…> would publish verbatim into the manifest. The GATE-1
cat latest.json review is the backstop; substitute it here so the gate confirms, not fixes.
⚠️ signature = the .sig file contents VERBATIM. The .sig tauri produces is
ALREADY base64; the updater plugin base64-decodes the field once at verify time.
Do NOT re-encode it (base64 latest… / openssl base64 on the .sig → double-encoded
→ Signature::decode fails → every update rejects). The --arg sig "$SIG" above passes
it as-is — correct. (Empirically confirmed: verbatim .sig verifies; double-encoded fails.)
Sanity-check the manifest before the gate:
jq -e '.version and .platforms."darwin-aarch64".signature and .platforms."darwin-aarch64".url' latest.json
# signature field content must equal the .sig file content. Compare via $(...) on BOTH sides
# so the .sig's trailing newline (which jq strips from the stored field) doesn't false-alarm —
# a plain `diff` reports "\ No newline at end of file" even when the base64 is identical.
[ "$(jq -r '.platforms."darwin-aarch64".signature' latest.json)" = \
"$(cat src-tauri/target/release/bundle/macos/Claudesk.app.tar.gz.sig)" ] \
&& echo "sig verbatim OK" || echo "⚠️ signature field != .sig content — do NOT publish"⏸ GATE 1 — confirm before publishing. Show the operator:
- the built
.dmgpath + its size + the sha256, - the four assets that will upload (dmg +
Claudesk.app.tar.gz+.sig+latest.json), - the composed
latest.json(cat latest.json) — confirmversion,url, and thatsignatureis the verbatim.sig, and - the full drafted release notes.
Wait for explicit approval (and apply any edits the operator gives). Do NOT run step 7 until they say go — step 7 publishes publicly.
- the built
Tag + publish the GitHub release — with ALL FOUR assets. The
.dmg(first-install/Homebrew) plus the three updater artifacts (Claudesk.app.tar.gz, its.sig, andlatest.json) go up in onegh release create:git tag "v${VER}" git push origin "v${VER}" gh release create "v${VER}" \ "src-tauri/target/release/bundle/dmg/Claudesk_${VER}_aarch64.dmg" \ "src-tauri/target/release/bundle/macos/Claudesk.app.tar.gz" \ "src-tauri/target/release/bundle/macos/Claudesk.app.tar.gz.sig" \ "latest.json" \ --title "Claudesk v${VER}" \ --notes "<the approved notes from step 6>"Confirm all four asset names are present:
gh release view "v${VER}" --json assets --jq '.assets[].name' # expect: Claudesk_<VER>_aarch64.dmg, Claudesk.app.tar.gz, Claudesk.app.tar.gz.sig, latest.jsonThe dmg asset URL will be
https://github.com/StaymanHou/Claudesk/releases/download/v<VER>/Claudesk_<VER>_aarch64.dmg.Then confirm the updater ENDPOINT resolves — the exact URL the running app polls (
releases/latest/download/latest.json, which GitHub aliases to this release once it's the latest). Fetch it and confirm it's the manifest you just published:curl -sSL https://github.com/StaymanHou/Claudesk/releases/latest/download/latest.json | jq -e '.version == "'"$VER"'"' \ && echo "endpoint resolves → version $VER" \ || echo "⚠️ endpoint did NOT return version $VER — the app's check() will not see this update"(If this is a pre-release or not the newest tag,
latest/download/points elsewhere — the check is meaningful only when vVER is the newest published release, which is the normal/releasecase.)Bump the tap cask. In
homebrew-claudesk/Casks/claudesk.rb(nested in this project), update:version "VER"sha256 "<hash from step 4>"
The
urlis version-interpolated (v#{version}/#{version}), so it does not need editing. Validate against the installed tap copy (audit/style read the INSTALLED copy, not the working tree):cp homebrew-claudesk/Casks/claudesk.rb \ "$(brew --repository)/Library/Taps/staymanhou/homebrew-claudesk/Casks/claudesk.rb" brew audit --cask staymanhou/claudesk/claudesk # must be clean (no output) brew style staymanhou/claudesk/claudesk # must be cleanIf audit or style fails, fix the cask and re-validate before the gate.
- ⏸ GATE 2 — confirm before pushing the tap. Show the operator the cask diff
(
git -C homebrew-claudesk diff Casks/claudesk.rb) and the clean audit/style results. Wait for explicit approval before step 10. Push the tap:
git -C homebrew-claudesk commit -am "claudesk VER" git -C homebrew-claudesk push origin HEADClean up the transient manifest, then report. Remove the repo-root
latest.json(it's already uploaded to the release; leaving it dirties the working tree and would trip the clean-tree precondition on the next run — it's also gitignored as a backstop):rm -f latest.jsonThen report to the operator: the release URL, the tap cask commit, and the one-paste install command. Record the build time in
runtimes.mdif it was a fresh measurement.
Notes & gotchas (learned 2026-06-24 on the v0.1.0 cut)
- Homebrew 6.x removed
--no-quarantine. Do NOT putbrew install --cask --no-quarantine claudeskin release notes or the README — it errors with "invalid option: --no-quarantine". ⚠️ The flag is still gone, but the reason it mattered is not: as of v0.5.2 the build is notarized, so plainbrew install --cask claudeskjust works with no follow-up command at all. (Signing + notarization will remove this step entirely — a deferred M9 upgrade.) - Third-party-tap trust gate. Recent Homebrew refuses casks from untrusted
taps. Friends run
brew trust --cask StaymanHou/claudesk/claudeskonce. Keep this in the tap README's install block. - Cask
verified:param. Don't addverified:to theurlwhen the url domain == homepage domain (bothgithub.com) —brew auditrejects it as unnecessary. brew audit/brew styleread the INSTALLED tap copy, not your working tree. Alwayscpyour editedclaudesk.rbinto$(brew --repository)/Library/Taps/staymanhou/homebrew-claudesk/Casks/before auditing, or push first andbrew update.- Two repos, two pushes. The app code/tag/release goes to
StaymanHou/Claudesk; the cask bump goes toStaymanHou/homebrew-claudeskviagit -C homebrew-claudesk. They are independent repos nested on disk (the tap is gitignored by claudesk) — a push to one never touches the other. - ⚠️ SIGNED + NOTARIZED as of v0.5.2 — this REVERSES the M10 decision (M14 WP2,
2026-09-18). Builds are Developer-ID signed with the hardened runtime and
Apple-notarized, so
spctlreportssource=Notarized Developer IDand Gatekeeper admits them unaided. Thexattrstep is deleted everywhere — from release notes and the README — and the updater's post-install self-quarantine-clear was removed with it. ⚠️ minisign is RETAINED, not replaced: the two systems are independent (minisign verifies the updater payload insidedownload(); notarization satisfies Gatekeeper via a stapled ticket), and the trust anchor774E2E8429FDF78Ais unchanged — changing it would strand every existing install. Apple-Silicon-only is unchanged. Seeworkflow-system/product/arch/build-update-release.md. (Supersedes both the earlier "Notauri-plugin-updateryet — friends re-brew upgrade" note (the updater shipped at M10 WP2) and the M10 "stay unsigned + minisign" lock.) - Updater signing (M10 WP5) — two gotchas that silently break updates if missed.
TAURI_SIGNING_PRIVATE_KEYis the key CONTENTS (a string), NOT a path. The build's integrated sign step readsTAURI_SIGNING_PRIVATE_KEY(+..._PASSWORD). If you set onlyTAURI_SIGNING_PRIVATE_KEY_PATH, the build completes bundling then exits 1 with "A public key has been found, but no private key…" and ships an unsigned.tar.gz(no.sig). Alwaysexport TAURI_SIGNING_PRIVATE_KEY="$(cat ~/.claudesk-release-keys/claudesk-release.key)"(step 3). The.sig-present guard in step 3 catches a missed export.latest.jsonsignature= the.sigcontents VERBATIM — do NOT re-base64-encode. Tauri's.sigis already base64; the updater plugin base64-decodes the field once at verify time. Re-encoding →Signature::decodefails → every update is rejected. Step 5b's--arg sig "$SIG"passes it as-is; thediffsanity-check confirms byte-identity.
- First updatable release is the FLOOR, not retroactive. The in-app updater only updates
from a build that already contains it (M10 WP2 = the first). The first
/releasecut after M10 ships is the floor: it publishes the updater artifacts, but users on older builds (v0.2.x) mustbrew upgrade/ re-download once to land on an updater-capable version — thereafter they self-update. A key rotation (changingplugins.updater.pubkey) resets this floor: builds signed with the old key can't verify a new-key update, so a rotation also forces a one-timebrew upgrade/re-download. Keep the key (774E2E8429FDF78A) stable across releases. - Homebrew installs never self-update — detect-and-defer (M10 WP3). A brew-cask install of
Claudesk resolves to a
/Caskroom/path; the updater detects this and defers tobrew upgraderather than self-installing (avoids brew version desync). So the tap-cask bump (steps 8–10) remains the update path for brew users; the in-app updater serves direct-download installs only. Nothing to do here beyond the normal cask bump — noted so the two paths aren't conflated.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

