From d9394e6afb1c9783acad5774e83b8e5bbeb8b0cd Mon Sep 17 00:00:00 2001 From: Hardik Date: Sun, 21 Jun 2026 02:09:18 +0530 Subject: [PATCH] docs(release): make the v-prefixed tag requirement prominent deploy.yml only triggers on v* tags; bare semver tags (0.2.0/0.2.1/0.2.2) silently do not deploy. Clarify: push the v* tag specifically (not 'master --tags'). Co-Authored-By: Claude Opus 4.8 --- automation/README.md | 16 +++++++++++----- 1 file changed, 11 insertions(+), 5 deletions(-) diff --git a/automation/README.md b/automation/README.md index af8b00d..76e3c03 100644 --- a/automation/README.md +++ b/automation/README.md @@ -161,16 +161,22 @@ portal ──(triage)──▶ triaged + claude-queue ─▶ claude-working ─ ## Releasing -After merging a Claude PR (or any change) on `master`: +> ⚠️ **Release tags MUST be `v`-prefixed** (e.g. `v0.2.2`). `deploy.yml` triggers only on +> `v*` tags — a bare tag like `0.2.2` will **NOT** deploy (the runner ignores it and prod +> stays on the previous version). Push the **tag** specifically; pushing `master` alone +> never deploys. + +After merging PR(s) on `master`: ```powershell git pull -git tag v0.2.0 # semver: bump patch for fixes, minor for features -git push pms1 master --tags +git tag v0.2.2 # MUST start with "v"; semver: patch = fixes, minor = features +git push pms1 v0.2.2 # pushing the v* tag is what triggers the deploy ``` -The runner deploys the tag and restarts the app. Watch progress under -**Actions** on the Forgejo repo, or `pm2 logs forgejo-runner` on pms1. +The runner checks out the tag in `~/pms`, runs `pnpm install` + `build` + +`prisma migrate deploy`, `pm2 restart ppms`, and verifies `/login` returns 200. Watch +progress under **Actions** on the Forgejo repo, or `pm2 logs forgejo-runner` on pms1. ## Operational notes