release-daylisted

<!-- Generated by scripts/build-adapters.sh. Do not edit directly. --> > 🤖 *Auto-generated by **weekly-pattern-learner** · changelog-generator, store-listing-copy, and apple-store-submit each reference each other in their Chaining tables but no skill chains them into a single end-to-end release-day workflow* # Release Day Drive a release from "code is ready" to "build submitted" in one orchestrated pass. Each phase validates its output before proceeding: the skill stops and reports rather than pushing a broken release. ## Inputs - **Platform** (required): `ios`, `android`, `garmin`, or `all` - **Version** (optional): explicit version to release; if omitted, semantic-release determines the next version automatically - **Branch** (optional, default: `main`): branch to release from - **--dry-run** (optional): run all checks and generate all copy without pushing the tag or submitting to the store ## Phase 1: Verify the branch is ready ```bash BRANCH="${Branch:-main}" git fetch origin "$BRANCH" BRANCH_SHA=$(git rev-parse "origin/$BRANCH") # Validate optional Version input if [ -n "$Version" ]; then if ! echo "$Version" | grep -qE '^v?[0-9]+\.[0-9]+\.[0-9]+(-[a-zA-Z0-9.]+)?$'; then echo "Error: Version '$Version' is not a valid SemVer (e.g. 1.2.3 or v1.2.3)" >&2 exit 1 fi fi git status --short # Last release tag LAST_TAG=$(git describe --tags --abbrev=0 2>/dev/null || echo "none") # Commits since last release if [ "$LAST_TAG" = "none" ]; then git log "