Skip to content
Skills Library
DevOps & cloud · Automation

release

/release

Cut a PocketRocket release (signed arm64 APK on GitHub) the way this project does it. Use when Shankar asks to release, ship, publish a new version or APK, bump the version, write release notes, or asks why or where a release went.

Licence
Apache-2.0
Last repository change
05.11.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 05.11.2026, without references to retired models or APIs.

Licence

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

What it does and when to use it

Cut a PocketRocket release (signed arm64 APK on GitHub) the way this project does it. Use when Shankar asks to release, ship, publish a new version or APK, bump the version, write release notes, or asks why or where a release went.

Original author description

Cut a PocketRocket release (signed arm64 APK on GitHub) the way this project does it. Use when Shankar asks to release, ship, publish a new version or APK, bump the version, write release notes, or asks why or where a release went.

How it works

  1. Where releases go
  2. Versioning
  3. Signing
  4. Steps
  5. Rules
Original SKILL.md headings · 51 lines, 865 words
SKILL.md preview
---
name: release
description: Cut a PocketRocket release (signed arm64 APK on GitHub) the way this project does it. Use when Shankar asks to release, ship, publish a new version or APK, bump the version, write release notes, or asks why or where a release went.
---

# Releasing PocketRocket

Releases are built, signed and published by the **Release** workflow on GitHub Actions (`.github/workflows/release.yml`, decision 67). Start it with:

```
GH_TOKEN=$(gh auth token -u ShankarKakumani) gh workflow run release.yml -R dockito-ai/pocketrocket \
  --ref main -f version=X.Y.Z -f notes="$(cat notes.md)" [-f dry_run=true]
```

Shankar usually runs `scripts/ship.sh`, which pulls, asks the version, drafts notes in $EDITOR, offers a dry run and starts and follows the workflow. `scripts/release.sh X.Y.Z --notes FILE [--dry-run]` (or `scripts/ship.sh --local`) is the local fallback when Actions can't run; it needs the keystore and the Keychain password on the Mac. Background: decisions 26, 30, 63, 65, 67 and 83 in `docs/decisions.md`, plus `docs/app-updates.md`.

## Where releases go

- **`dockito-ai/pocketrocket`**: the code repo. The workflow publishes the release here on tag `vX.Y.Z`. The updater reads it first (`ReleaseSource.REPO`) once it's public.

Releases are full releases marked Latest (decision 90), with the title `PocketRocket X.Y.Z` and the asset `pocketrocket-vX.Y.Z-arm64.apk`.

## Versioning

- The version is the single line `def pocketRocketVersion = "X.Y.Z"` in `app/build.gradle`. On main it holds the **last released** version; the workflow bumps it with `scripts/set-version.sh`. Never bump it by hand.
- versionCode = 1000 + major*10000 + minor*100 + patch. For example, 1.0.5 → 11005.
- Pick the next patch unless Shankar says otherwise. The workflow refuses a version that isn't newer or whose tag exists.

## Signing

- The release key: PKCS12, alias `pocketrocket`, RSA 4096, one password for store and key. Its certificate SHA-256 is pinned in `scripts/release-cert.sha256` (`44b223b1…1d731048`); both the workflow and `release.sh` refuse a keystore or APK signed by anything else.
- On GitHub it lives in the repo's Actions secrets `RELEASE_KEYSTORE_BASE64` and `RELEASE_KEYSTORE_PASSWORD`, which **only Shankar adds** (commands in `docs/app-updates.md`). Never add, read, print or set them yourself.
- On the Mac: `~/.pocketrocket-keys/pocketrocket-release.jks`, password in the login Keychain (service `pocketrocket-release-key`, account `pocketrocket`) and in his Passwords app, backup in iCloud Drive under `PocketRocket Keys/`. **Never print it, echo it, or write it to a file or chat.**
- Never commit the key and never sign a release with anything else: a different key forces every user to uninstall and lose their data.

## Steps

0. **Only on Shankar's go.** Release only when he explicitly says to, for this version. He often keeps pushing from the phone, so a push or a "try now" is not a go. Until he says so, check CI is green on main and report that main is ready.
1. **Sync main.** `git pull --rebase` on main. CI (`.github/workflows/ci.yml`) runs the unit tests and a debug build on every push; it must be green on the commit you release.
2. **Write the notes** in the scratchpad, not the repo. Write them for Shankar's phone: short, plain words, what's new since the last tag (`git log vPREV..HEAD --oneline`), grouped by what he will notice. Only add an uninstall warning if the signing key or package id changed. The workflow appends the code link and the `SHA-256:` line the updater checks, so don't add them.
3. **Dry run:** the command above with `-f dry_run=true`. It builds and signs (with a throwaway key if the secrets aren't set), runs every check and prints the planned commands and notes in the run summary. It never commits, tags, pushes or releases. Dry runs may use any branch; real runs only main.
4. **Real run:** the same without `dry_run`. The build job checks the version, sets it, builds and signs the arm64 APK, checks package, version and signer, hashes it and writes the notes. The publish job then checks main hasn't moved, commits `Release vX.Y.Z` as Shankar's noreply identity, tags, pushes main and the tag together, and creates the release, marked Latest. Follow it with one `gh run watch <id> -R dockito-ai/pocketrocket --exit-status`, not a polling loop.
5. **Verify** with `GH_TOKEN=$(gh auth token -u ShankarKakumani) gh release view vX.Y.Z -R <repo>` on each repo it published to. The asset digest must match the SHA-256 in the run summary.
6. **Log it.** Pull main (the workflow pushed the bump), add a line under today's date in `docs/PROGRESS.md` with the version, the versionCode and the link, then commit and push.
7. **Tell Shankar** in a few lines: the link, what's in the release, and how to get it (Settings › PocketRocket › Update, or install from the link).

## Rules

- Git identity is `Shankar Kakumani <ShankarKakumani@users.noreply.github.com>`. Add no Co-Authored-By or AI attribution lines to commits or release notes.
- Never bundle Claude Code in the APK. It's downloaded at first run.
- Keep personal info out of release notes and the APK: no emails, Mac paths or other projects' names.
- The package id is `app.pocket` (decision 36). Don't change it; a different id is a different app and won't update.
- If a run fails after the push but before the release exists, don't rerun it: the version is already bumped and tagged. Download the run's `release` artifact (`gh run download <id> -n release`) and create the missing release by hand with the `gh release create` line from the run summary (`--verify-tag` on the code repo).
- Per the global CLAUDE.md, a long release can go to a Sonnet agent. Name the model on the spawn.

Versions

RepositoryScoreLicence
This page · dockito-ai/pocketrocket100Apache-2.0
josephfung/curia100MIT
max-sixty/worktrunk100MIT
gtapps/hermitd100MIT
gtapps/hermitd100MIT
anthony-chaudhary/fak100Apache-2.0
tractorjuice/arc-kit100MIT
drvoss/everything-copilot-cli100MIT
sma1lboy/rove100MIT

Database snapshot: 13.11.2026 · package version bf1a9dfe5ea8 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100new-version
    Releases a new version of the RightSubs APK — picks the number (semver), updates VERSION and CHANGELOG, commits, creates the vX.Y.Z tag and, when the user asks, pushes it so GitHub Actions builds, signs and publishes the release. Use when the user asks for a new version, a…
  • 100create-release
    Use when the user asks to "create a release", "cut a release", "tag a version", "publish release notes", or ship a new versioned GitHub release for the current repo.
  • 90paw-tools-release
    Automates software releases from version bump to GitHub release. Use when the user requests to 'create a release', 'cut a release', 'publish a new version', or 'prepare a release'.
  • 100ls-release
    Cut a LlamaStash release (vX.Y.Z) end to end - promote the CHANGELOG, bump Cargo.toml and the TUI goldens, commit and push, tag, watch the publish pipeline, write the GitHub release body, verify every channel. Use when asked to release, ship, or publish a new version of llamastash.
  • 100android-release-pipeline
    FrostWire for Android release pipeline - dated, importance-sorted changelog, tag frostwire-android-<version>-build-<build>, GitHub release with a plain-language post and the signed APK, then the frostwire.com config.php update and pull on virginia1. Includes the…
  • 96making-a-release
    Use when a developer wants to cut, publish, or ship a new release of the CodeScene MCP Server, or asks how to make a release / bump the version.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.