shad0w/pelagia-portal
1
0
Fork 0
Code Issues 6 Pull requests Projects Releases 2 Packages Wiki Activity Actions

docs(release): make the v-prefixed tag requirement prominent
All checks were successful
PR checks / checks (pull_request) Successful in 31s
Details

Browse source 
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 <noreply@anthropic.com>
This commit is contained in:
Hardik 2026-06-21 02:09:18 +05:30
parent 6137d11e5f
commit d9394e6afb
1 changed files with 11 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

16
automation/README.md
View file

@ -161,16 +161,22 @@ portal ──(triage)──▶ triaged + claude-queue ─▶ claude-working ─
## Releasing ## 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 ```powershell
git pull git pull
git tag v0.2.0 # semver: bump patch for fixes, minor for features git tag v0.2.2 # MUST start with "v"; semver: patch = fixes, minor = features
git push pms1 master --tags 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 The runner checks out the tag in `~/pms`, runs `pnpm install` + `build` +
**Actions** on the Forgejo repo, or `pm2 logs forgejo-runner` on pms1. `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 ## Operational notes