BlueGit

timfa containerpipes

cursor rule

timfa Tim Falken · pushed by timfa

Authored 2026-08-11 · 3 months ago

Hash
367f8cfe99be565797557aac8cc26e4529adb869
Parent
e7e285c2
1 file changed +40 −0
.cursor/rules/release-tags.mdc added +40 −0
@@ -0,0 +1,40 @@
1 ---
2 description: Release-tag format, when to create tags, and what the GitLab release pipeline does
3 alwaysApply: true
4 ---
5
6 # Release tags (ContainerPipes)
7
8 ## Tag format
9
10 - Allowed: `X.Y.Z` or `vX.Y.Z` (digits only, no prerelease suffix).
11 - Valid: `1.7.0`, `v1.7.0`, `1.7.10`, `1.8.0`
12 - Invalid: `1.7`, `v1.7.0-beta`, `release-1.7.0`, `1.07.0` (no leading zeros in a segment)
13
14 Prefer **no** `v` prefix in this repo (`1.7.0`), consistent with existing tags.
15
16 ## Creating a release
17
18 1. Ensure release-related changes are on `master` and pushed.
19 2. Create the tag on the intended commit (usually `HEAD` of `master`).
20 3. Push only the new tag: `git push origin <tag>`.
21 4. Do **not** force-update or move an existing protected tag. If a retry is needed on the same version, delete the tag in the GitLab UI first, then recreate it.
22
23 The new version must be **strictly greater** than the previous release tag (semver compare). The pipeline fails otherwise.
24
25 ## What the pipeline does on a version tag
26
27 Triggered by `.gitlab-ci.yml` when any tag is pushed:
28
29 1. **validate** — check format and that the version is newer than prior release tags
30 2. **bump** — set version in project files (`build.gradle.kts`, `plugin.yml`, READMEs, plugin log string), commit, push to default branch with `ci.skip` (tag is **not** moved; protected tags cannot be updated)
31 3. **build** — produce `ContainerPipes-<version>.jar`, upload to Package Registry
32 4. **release** — publish a GitLab Release with that jar
33 5. **rotate-token** — self-rotate `CI_PUSH_TOKEN` and write it back to CI/CD variables
34
35 ## Agent do / don't
36
37 - Do create/push a **new** version tag when the user asks to release or retag after they deleted the old tag.
38 - Do not rewrite/force-push protected tags; ask the user to delete via GitLab UI first.
39 - Do not invent non-semver tags for releases.
40 - After a failed release fix, push the fix to `master`, then recreate the version tag only if the remote tag is gone (or the user deleted it).
@@ -0,0 +1,40 @@
1---
2description: Release-tag format, when to create tags, and what the GitLab release pipeline does
3alwaysApply: true
4---
5
6# Release tags (ContainerPipes)
7
8## Tag format
9
10- Allowed: `X.Y.Z` or `vX.Y.Z` (digits only, no prerelease suffix).
11- Valid: `1.7.0`, `v1.7.0`, `1.7.10`, `1.8.0`
12- Invalid: `1.7`, `v1.7.0-beta`, `release-1.7.0`, `1.07.0` (no leading zeros in a segment)
13
14Prefer **no** `v` prefix in this repo (`1.7.0`), consistent with existing tags.
15
16## Creating a release
17
181. Ensure release-related changes are on `master` and pushed.
192. Create the tag on the intended commit (usually `HEAD` of `master`).
203. Push only the new tag: `git push origin <tag>`.
214. Do **not** force-update or move an existing protected tag. If a retry is needed on the same version, delete the tag in the GitLab UI first, then recreate it.
22
23The new version must be **strictly greater** than the previous release tag (semver compare). The pipeline fails otherwise.
24
25## What the pipeline does on a version tag
26
27Triggered by `.gitlab-ci.yml` when any tag is pushed:
28
291. **validate** — check format and that the version is newer than prior release tags
302. **bump** — set version in project files (`build.gradle.kts`, `plugin.yml`, READMEs, plugin log string), commit, push to default branch with `ci.skip` (tag is **not** moved; protected tags cannot be updated)
313. **build** — produce `ContainerPipes-<version>.jar`, upload to Package Registry
324. **release** — publish a GitLab Release with that jar
335. **rotate-token** — self-rotate `CI_PUSH_TOKEN` and write it back to CI/CD variables
34
35## Agent do / don't
36
37- Do create/push a **new** version tag when the user asks to release or retag after they deleted the old tag.
38- Do not rewrite/force-push protected tags; ask the user to delete via GitLab UI first.
39- Do not invent non-semver tags for releases.
40- After a failed release fix, push the fix to `master`, then recreate the version tag only if the remote tag is gone (or the user deleted it).