Skip to content
Back to skills

2528 Releasing F6b07c11

ASecurity

This repo ships via GitHub Releases. When you push a tag like `v0.1.0`, GitHub Actions will: - build a universal macOS app bundle - code sign it (Developer ID Application) - notarize it - attach the signed/notarized `.dmg` to a draft GitHub Release for that tag

  • 9 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 11, 2026
devopsgogit

Security analysis

A100/100

Scanned October 11, 2026

npx -y skills add tools-only/X-Skills --skill 2528-releasing_f6b07c11 --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of 2528 Releasing F6b07c11?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for 2528 Releasing F6b07c11
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/tools-only-2528-releasing-f6b07c11/badge)](https://www.skillsdirectory.com/skills/tools-only-2528-releasing-f6b07c11)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

SKILL.md
# Releasing Brood (macOS)

This repo ships via GitHub Releases.

When you push a tag like `v0.1.0`, GitHub Actions will:
- build a universal macOS app bundle
- code sign it (Developer ID Application)
- notarize it
- attach the signed/notarized `.dmg` to a draft GitHub Release for that tag

## One-Time Setup (GitHub Repo Secrets)

Set these secrets in your GitHub repository:

- `APPLE_CERTIFICATE`: Base64-encoded `.p12` containing your **Developer ID Application** certificate.
- `APPLE_CERTIFICATE_PASSWORD`: Password for the `.p12`.
- `APPLE_ID`: Apple ID email used for notarization.
- `APPLE_PASSWORD`: App-specific password (or notarization password) for `APPLE_ID`.
- `APPLE_TEAM_ID`: Your Apple Team ID (example: `JU3DQ69K6R`).

Notes:
- The workflow imports the certificate into a temporary build keychain and auto-detects the `Developer ID Application` identity to use.
- The workflow enforces `tag == v${tauri.conf.json package.version}` to avoid accidental mismatches.

## Cut A Release

1. Update versions (must match):
   - `desktop/package.json` `version`
   - `desktop/src-tauri/tauri.conf.json` `package.version`
   - `desktop/src-tauri/Cargo.toml` `[package].version`
2. Update `CHANGELOG.md`.
3. Commit the changes.
4. Tag and push:
   - `git tag vX.Y.Z`
   - `git push origin vX.Y.Z`
5. Wait for the `publish` workflow to finish.
6. Publish the draft release on GitHub (or change `releaseDraft` to `false` in the workflow once you're confident).

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…