docs(release): make v-prefixed tag requirement prominent #52

Merged

shad0w merged 2 commits from docs/release-tag-warning into master

2026-06-20 21:15:43 +00:00

shad0w commented

2026-06-20 20:39:22 +00:00

Owner

Makes the v-prefixed release tag requirement prominent in automation/README.md → Releasing.

Context: tags 0.2.0/0.2.1/0.2.2 were pushed but didn't deploy because deploy.yml only triggers on v*; prod stayed on v0.1.2. Clarifies that you push the v* tag itself (not master --tags). Docs-only.

Optional follow-up (not in this PR): broaden deploy.yml to also accept bare semver tags so this can't trip anyone up — say the word and I'll do it.

Makes the **`v`-prefixed release tag** requirement prominent in automation/README.md → Releasing. Context: tags `0.2.0`/`0.2.1`/`0.2.2` were pushed but didn't deploy because `deploy.yml` only triggers on `v*`; prod stayed on `v0.1.2`. Clarifies that you push the `v*` tag itself (not `master --tags`). Docs-only. Optional follow-up (not in this PR): broaden `deploy.yml` to also accept bare semver tags so this can't trip anyone up — say the word and I'll do it.

shad0w added 1 commit 2026-06-20 20:39:22 +00:00

docs(release): make the v-prefixed tag requirement prominent

PR checks / checks (pull_request) Successful in 31s

Details

d9394e6afb

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>

shad0w added 1 commit 2026-06-20 21:14:48 +00:00

Merge branch 'master' into docs/release-tag-warning

PR checks / checks (pull_request) Successful in 33s

Details

8ee077e548