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-electron-<version>` tag, push the release-prep commit, and verify the GitHub Actions package flow. Prefer this over a generic GitHub release process for Atmos desktop releases. Publishes the production Electron desktop shell only (Tauri desktop release is deprecated). On packaging CI failure, prefer re-run or same-version retag over auto-bumping beta.N+1 (see Failure recovery).
AruNi-01/atmos · ★ 6 · Web & Frontend · score 72

Install: claude install-skill AruNi-01/atmos

Atmos-specific **production desktop** release workflow (Electron ship path). ## What this skill owns 1. validate repository state 2. bump `apps/desktop-electron/package.json` 3. create/push `desktop-electron-<version>` 4. generate release notes under `releasenotes/` 5. let `.github/workflows/release-desktop-electron.yml` package and publish **Does not** run the deprecated Tauri workflow (`release-desktop.yml` / Homebrew-only Tauri path). ## Execution ```bash # standard node ./.agents/skills/atmos-desktop-release/scripts/atmos-desktop-release.mjs <version> # dry-run node ./.agents/skills/atmos-desktop-release/scripts/atmos-desktop-release.mjs <version> --dry-run # prerelease node ./.agents/skills/atmos-desktop-release/scripts/atmos-desktop-release.mjs <version> --prerelease ``` Equivalent just recipes: ```bash just release-desktop <version> just release-desktop-dry-run <version> ``` ## Repository model (production) | Item | Value | |------|--------| | Tag | `desktop-electron-<version>` | | Version file | `apps/desktop-electron/package.json` | | App id | `com.atmos.desktop` | | Product name | `Atmos` | | Workflow | `.github/workflows/release-desktop-electron.yml` | | Notes | `releasenotes/Atmos Desktop <version>.md` (preferred) | ## Release notes writing Generate `releasenotes/Atmos Desktop <version>.md` from the collected commit/PR context and the template in `references/release-notes-template.md`. After the product narrative, **always end the file with