release skillA
release is agent-read markdown (skill) from nikships/droidproxy: Build, sign, notarize, and publish a new DroidProxy release. Use when the user wants to cut a release, merge a PR and ship it, or asks to build/notarize/publish. Covers the full pipeline: PR merge, version bump, swift build, code signing, Apple notarization, Sparkle appcast update, and GitHub release creation..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# DroidProxy Release End-to-end release pipeline for DroidProxy macOS menu bar app. ## Prerequisites - Developer ID signing identity available in keychain - `notarytool` keychain profile named `"notarytool"` configured - Sparkle EdDSA signing key in keychain (used by `sign_update`) - `gh` CLI authenticated with push access to `anand-92/droidproxy` - On the `main` branch with a clean working tree ## Steps ### 1. Determine version Check the latest git tag and the commits being released to decide the new semver: ```bash git tag --sort=-v:refname | head -5 git log --oneline $(git describe --tags --abbrev=0)..HEAD ``` - New feature -> bump minor (e.g. 1.5.0 -> 1.6.0) - Bug fix only -> bump patch (e.g. 1.5.0 -> 1.5.1) - CLIProxyAPI bump alone -> bump patch ### 2. Bump version in Info.plist Edit `src/Info.plist` and update `CFBundleShortVersionString` to the new version. ### 3. Build the app bundle ```bash APP_VERSION=<version> ./create-app-bundle.sh ``` This does a release swift build from `src/`, assembles the `.app` bundle, signs everything (cli-proxy-api, Sparkle.framework, main executable) with Developer ID, and verifies. …
Read the whole file at its exact version.
How to install
mdr add nikships/droidproxy/release@v1.0.0mdr add nikships/droidproxy/release@sha256:b58b71c0e14a34a8Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_qkuvtkfad4kohhbl)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.0.0 latest | 2026-05-30 | 807d528 | 4,394 B | A | view · diff |
| v1.0.0 | 2026-04-08 | bac02ff | 4,409 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (4394 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
nikships/droidproxy · 121 stars · license MIT · pushed 2026-09-24 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_qkuvtkfad4kohhbl GET https://markdownregistry.com/api/v1/resolve?ref=nikships/droidproxy/release GET https://markdownregistry.com/api/v1/blob/b58b71c0e14a34a8f97ed4e1cc1bd4a3233fe2ab22c82d7ca4e88a7b3543c151
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
More from nikships/droidproxy
Every file in nikships/droidproxy