Skip to content

2001105254-netizen/RacePulsePH / .agents/skills/racepulse-github-release-cicd

racepulse-github-release-cicd

Verified

Automate RacePulsePH semantic versioning, commit hooks, always-RacePulsePH Android APK/AAB naming, GitHub Actions CI/CD, and standard GitHub Releases. Use when setting up CI/CD workflows, versioning hooks, or publishing app releases.

FileKindSize
SKILL.mdskill md3.4 KB
references/checklist.mdmarkdown3.1 KB

references/checklist.md

View on GitHub
# CI/CD release pipeline checklist

Standard release engineering workflow for RacePulsePH versioning, Android packaging (`RacePulsePH.apk` and `RacePulsePH.aab`), and automated GitHub Releases.

## 1. Per-commit versioning (`.githooks/pre-commit`)

1. Ensure `.gitattributes` keeps `.githooks/*` and shell scripts in LF line endings on Windows and Linux.
2. Run `npm run hooks:install` (`node scripts/setup-git-hooks.cjs`) once per clone (also triggered by `npm install` via `"prepare"`).
3. On each normal commit, `.githooks/pre-commit` executes `node scripts/release-version.cjs --auto --stage`:
   - If the author already bumped SemVer and `versionCode` relative to `HEAD` (for instance via `npm run version:minor` or `npm run version:major`), `--auto` preserves that bump and keeps all tracked files synced.
   - Otherwise, `--auto` increments SemVer patch (`X.Y.Z` to `X.Y.(Z+1)`) and Android `versionCode` (`N` to `N+1`), updates `package.json`, `package-lock.json`, `android/app/build.gradle`, and `rfid-station/RacePulseTimingStation.iss`, and stages them into the commit.
4. Set `SKIP_VERSION_BUMP=1` only when intentionally keeping the current version (for instance `git commit --amend`). Merges, rebases, and cherry-picks skip auto-bumping cleanly.

## 2. Standard Android release naming and signing (`scripts/build-android-release.cjs`)

1. `android/app/build.gradle` configures `base.archivesName = "RacePulsePH"`, forces release APK output `RacePulsePH.apk`, and copies release bundles to `RacePulsePH.aab`.
2. Required environment variables or Gradle properties for signed builds:
   - `KEYSTORE_PATH` (or `RELEASE_STORE_FILE`)
   - `KEYSTORE_PASSWORD` (or `RELEASE_STORE_PASSWORD`)
   - `KEYSTORE_ALIAS` (or `RELEASE_KEY_ALIAS`)
   - `KEYSTORE_ALIAS_PASSWORD` (or `RELEASE_KEY_PASSWORD`)
3. Run `npm run release:android -- --require-signed` to sync Capacitor assets, build both release binaries, verify signatures with `apksigner verify` and `jarsigner -verify`, stage assets under `release/android/`, and emit `SHA256SUMS.txt`.

## 3. GitHub Actions CI/CD (`.github/workflows/ci-cd-release.yml`)

Configure these repository secrets under GitHub Settings -> Secrets and variables -> Actions (or run `scripts/configure-github-release-secrets.ps1 -Repo <owner/repo>`) before running `android-release`:

| Secret | Value |
| --- | --- |
| `ANDROID_KEYSTORE_BASE64` | Base64-encoded release `.jks` keystore file |
| `ANDROID_KEYSTORE_PASSWORD` | Keystore password |
| `ANDROID_KEYSTORE_ALIAS` | Signing key alias |
| `ANDROID_KEY_PASSWORD` | Key password for the signing alias |
| `GOOGLE_SERVICES_JSON_BASE64` | Base64-encoded `android/app/google-services.json` (optional if Firebase Google Services JSON is omitted) |

Release channels:

- **`main` push or dispatch:** creates/updates tag `v<version>` as the latest standard GitHub Release.
- **`QA` push or dispatch:** creates/updates tag `v<version>-qa.<versionCode>` as a GitHub pre-release so QA tags never collide when merged to `main`.
- Attached release assets on every release: `RacePulsePH.apk`, `RacePulsePH.aab`, `RacePulsePH.apk.sha256`, `RacePulsePH.aab.sha256`, and `SHA256SUMS.txt`.

writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 322kUpdated Claude CodeCodexVerifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 118kUpdated Claude CodeCodexVerifiedInstall