← ClaudeAtlas

atmos-desktop-releaselisted

Run the Atmos desktop release workflow for this repository. Use this whenever you need to cut an Atmos desktop release, bump the desktop version, create the required `desktop-v<version>` tag, push the release-prep commit, and verify the GitHub Actions + Homebrew tap flow. Prefer this over a generic GitHub release process for Atmos desktop releases.
AruNi-01/atmos · ★ 2 · Web & Frontend · score 69
Install: claude install-skill AruNi-01/atmos
Atmos-specific desktop release workflow. This skill is intentionally tied to this repository's release model. Use it when you want the standard Atmos desktop release path instead of a generic GitHub release flow. ## What this skill owns This skill handles the Atmos desktop release sequence: 1. validate repository state 2. bump desktop version files together 3. validate version consistency 4. create and push the `desktop-v<version>` tag 5. collect release context from GitHub using `gh` 6. generate the final release body with the model using that context 7. write the generated markdown to `releasenotes/<release title>.md` 8. commit that file as part of the release-prep change 9. let the publish workflow read that file and apply it to the GitHub Release 10. verify the Homebrew tap sync path The repository-specific implementation lives in the bundled script: - `scripts/atmos-desktop-release.mjs` Use that script for execution. Keep this file focused on orchestration and decision-making. ## Repository release model Atmos desktop releases follow these rules: - desktop tag format is `desktop-v<version>` - desktop versions must stay aligned across: - `apps/desktop/src-tauri/Cargo.toml` - `apps/desktop/src-tauri/tauri.conf.json` - `apps/desktop/package.json` - desktop release workflow: - `.github/workflows/release-desktop.yml` - Homebrew tap sync workflow: - `.github/workflows/sync-homebrew-tap.yml` - shared Homebrew tap: - `AruNi-01/homebrew-tap` Do not replace