release
Skill7 starsChanged 2 days agoMITView on GitHub
Cut a release of the Orbit clients by creating and pushing one vX.Y.Z git tag, which triggers the macOS release (signed + notarized DMG), the iOS release (TestFlight build) and the Android release (signed APK on the same GitHub Release) from the same tag. Use whenever someone wants to cut/ship a release, tag a version, push a TestFlight, beta or Android build, or kick off a release build.
- Commits and pushes
193 other projects use a version of this.
Adopted by
Most recently taken up by
- naomiaro/waveform-playlisttheir own version, first seen Nov 16, 2026
- osmlab/name-suggestion-indextheir own version, first seen Nov 16, 2026
- vulnerability-lookup/vulnerability-lookuptheir own version, first seen Nov 16, 2026
- ClickHouse/mcp-clickhousetheir own version, first seen Nov 16, 2026
- bpatrik/pigallery2their own version, first seen Nov 16, 2026
- Shasnow/StarRailAssistanttheir own version, first seen Nov 16, 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
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
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 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
parcadeiSkillagent-context-isolation
Agent Context Isolation
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
- amruthpillai/reactive-resume★ 46ksame name
- reactive-resume/reactive-resume★ 46ksame 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.
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 0 are distinctive, and 4 are very specific to this project.
0
Common
Most of the 183 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 73
Watch the build and report the result: All five jobs run in the one release.yml run:
- Very specific: line 79
dmg(macOS): when green, the signed + notarized DMG is in the run's Artifacts and a GitHub Release. - Very specific: line 80
testflight(iOS): when green, the build is uploaded, then needs a few minutes of App Store Connect processing (and a one-time … - Very specific: line 87
Re-publishing Android: if dmg failed, Android is not attached.
“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
Cut a release (macOS + iOS + Android from one tag)
A release is a single git tag — vX.Y.Z. Pushing it runs every job of .github/workflows/release.yml
from that same tag, so one command ships all three clients together:
Job (in release.yml) | Output |
identity | Refuses the tag unless it is v + the root package.json version and carries a filled-in release-notes/<version>.md; every build job waits for it |
dmg | macOS: signed + notarized DMG, a GitHub Release whose body is those release notes, and the Sparkle auto-update appcast |
testflight | iOS: signed .ipa archived and uploaded to TestFlight |
android-build | Android: signed release APK (signing key from the android-internal environment) |
android-publish | Android: attaches orbit-android-<version>.apk, its .sha256 and android-update.json to the same GitHub Release dmg created; installed Android apps update themselves from it |
The root package.json version is the version of record, and the tag is that version with v. Every
surface derives from it: the GitHub Release, the DMG/.zip names and CFBundleShortVersionString, the
TestFlight marketing version (numeric, suffix stripped), the Android versionName, the runner binaries and
/dl/version.json, the Sparkle appcast and android-update.json. release.yml refuses a tag that disagrees
with the package, so the two cannot drift.
vX.Y.Z→ macOS stable channel (reaches everyone) + an iOS TestFlight build.vX.Y.Z-beta.N→ macOS beta channel (only users who enabled "Receive beta updates") + an iOS TestFlight build. The-beta.Nsuffix is a macOS/Sparkle concept; iOS strips it to a numeric marketing version (v0.2.0-beta.3→ TestFlight0.2.0), and the build number (commit count) carries the beta iteration on TestFlight.- Android, either way:
versionNameis the tag withoutv(0.2.0-beta.3, suffix kept) andversionCodeis the same commit count as the iOS build number. Every Android phone on an older version is offered the new one, beta or stable.
How to use
Pick the version.
release.sh nextprints the one tag to cut next, resolved from the package version alone (old tags are never read as a sequence): the package version itself while it has no tag yet (the release commit is prepared and waiting), otherwise the next beta in the current series, orX.Y.(Z+1)-beta.1once a stable version is the package version. It only prints. Confirm it before bumping; pass an explicit version for anything else (a stable release, or opening a new minor).A beta belongs to the version it precedes, not the one already out.
0.1.1-beta.2sorts below0.1.1, so onceX.Y.Zships stable, its betas are spent — the next beta must open onX.Y.(Z+1).nexthandles the bump.Bump the package and open the notes. This is the release commit:
package.json, the lockfile andrelease-notes/<version>.mdall name the same version..claude/skills/release/release.sh bump next # or: bump 0.2.0-beta.3bump nextwhile the package version is still untagged and its notes exist changes nothing.Fill in every section of the notes file (
docs/release-notes-template.md), commit it, and make sure the branch ismainsynced withorigin/mainbefore tagging. Tagging a feature/session branch — or amainthat's behindorigin/main— ships a tree that's missing whatever landed onmainin parallel, so the release silently drops those features and can revert already-merged fixes.git rev-parse --abbrev-ref HEAD # → main git fetch origin && git rev-list --count HEAD..origin/main # → 0 (nothing on origin/main you're missing)Tag it (resolves the repo root itself). It runs the same identity gate as CI, refuses a dirty tree, a tag that disagrees with
package.json, missing or placeholder notes, and an already-used tag (local or remote), then creates an annotated tag and pushes it:.claude/skills/release/release.sh 0.2.0-beta.3 # the version package.json already carriesWatch the build and report the result. All five jobs run in the one
release.ymlrun:gh run watch "$(gh run list --workflow release.yml -L 1 --json databaseId -q '.[0].databaseId')"dmg(macOS): when green, the signed + notarized DMG is in the run's Artifacts and a GitHub Release.testflight(iOS): when green, the build is uploaded, then needs a few minutes of App Store Connect processing (and a one-time export-compliance answer) before it shows up in TestFlight.android-build/android-publish(Android):android-publishwaits fordmgandandroid-build; when green, the release listsorbit-android-<version>.apk, its.sha256andandroid-update.json(gh release view vX.Y.Z --json assets -q '.assets[].name'), and the job's summary shows their SHA-256. If the commit already went out for Android under another tag,android-buildsays so and both Android jobs end without publishing; that is not a failure.- Re-publishing Android: if
dmgfailed, Android is not attached. Fix the cause, then use Re-run failed jobs on that run (gh run rerun <run-id> --failed): the DMG is built again and the APKandroid-buildalready made is attached after it. Anandroid-buildthat refused the version (the commit count must grow) needs a new commit and a new tag.
Notes
.agents/skills/release/carries the same rules for other engines; itsscripts/release.shis thisrelease.sh, byte for byte (npm run test:release-identitychecks it). Change both together.- Accepted:
X.Y.Z(stable) orX.Y.Z-beta.N(macOS beta channel). iOS always ships the numericX.Y.Zto TestFlight regardless of suffix. - One tag fires all three — every
v*tag also uploads an iOS TestFlight build (twomacos-15runner jobs) and publishes Android (twoubuntu-24.04jobs). To build only one Apple platform, skip the tag and dispatch with theplatforminput:gh workflow run release.yml --ref main -f platform=macos(or-f platform=ios). A dispatch with no tag builds each client's default version. Android has no dispatch: it builds and publishes onv*tag pushes only.android-v*tags are retired and start nothing. - Required secrets are in the
release.ymlheader:- macOS
dmg:DEVID_CERT_P12_BASE64,DEVID_CERT_PASSWORD,KEYCHAIN_PASSWORD,APPLE_ID,APPLE_TEAM_ID,APPLE_APP_PASSWORD,SPARKLE_ED_PRIVATE_KEY. - iOS
testflight:ASC_KEY_ID,ASC_ISSUER_ID,ASC_KEY_P8_BASE64,APPLE_TEAM_ID. - Android
android-build: theandroid-internalenvironment (v* tags only) — secretsANDROID_KEYSTORE_BASE64,ANDROID_STORE_PASSWORD,ANDROID_KEY_ALIAS,ANDROID_KEY_PASSWORD, variablesANDROID_APPLICATION_ID,ANDROID_CERT_SHA256(seesrc/android/docs/release.md).
- macOS
To undo a tag pushed by mistake (one run holds all the jobs):
git push origin :refs/tags/vX.Y.Z # delete remote tag git tag -d vX.Y.Z # delete local tag gh run cancel <run-id> # stop the release.yml run if it already startedOnce
android-publishhas attachedandroid-update.json, installed Android apps may already be offered that version: say so when reporting the mistake rather than quietly deleting the release.
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.

