releaselisted

# Release Desktop Trigger `wibus-wee/cradle-app`'s `release-desktop.yml` workflow and monitor it until the release is published. ## Usage ```bash /release dev # Dev channel: dev-YYYYMMDD.N /release 1.2.0 # Release channel: v1.2.0 ``` ## Rules - Release tags live in this repository (`wibus-wee/cradle-app`). Tag the commit you want to ship (usually `origin/main`). - The workflow builds the tagged commit itself (or the pushed `main` SHA for bleeding-edge). There is no separate private source repo and no `PRIVATE_REPO_PAT` self-checkout. - Channels: - `bleeding-edge` — every push to `main` - `dev` — `dev-YYYYMMDD.N` tags - `release` — `vX.Y.Z` tags (stable) - Leave unrelated local files alone, including untracked workflow drafts. - Use Cradle awaits for workflow completion; do not watch the run with a long polling loop. - Use only short bounded retries to let GitHub materialize run/check IDs. ## Version Logic - `dev` creates `dev-YYYYMMDD.N`. - Use remote tags, not releases, to find the next increment. - Example: `dev-20260611.1`, then `dev-20260611.2`. - A release version creates `vX.Y.Z`. - Accept `1.2.0` or `v1.2.0`; normalize to `v1.2.0`. ## Implementation When the user runs `/release <arg>`, execute these steps in order. ### 1. Resolve tag ```bash cd "$(git rev-parse --show-toplevel)" git fetch origin main --tags ARG="<user argument>" if [ "$ARG" = "dev" ]; then DATE=$(date +%Y%m%d) LAST=$( git ls-remote --tags --refs origin "