From fb9bbce9eb3fd3d284f757d7fc9e0848d560452f Mon Sep 17 00:00:00 2001 From: aseimel Date: Tue, 30 Jun 2026 00:02:00 +0200 Subject: [PATCH] Clean release version references --- RELEASE.md | 11 +++++------ 1 file changed, 5 insertions(+), 6 deletions(-) diff --git a/RELEASE.md b/RELEASE.md index 7fd0b4b..6dabd2d 100644 --- a/RELEASE.md +++ b/RELEASE.md @@ -3,13 +3,12 @@ This project uses simple internal release tags: ```text -v1 -v2 -v3 -... +v ``` -Do not use semantic version tags such as `v1.0.0`. +Do not use semantic version tags such as `vX.Y.Z`. + +The current public release is `v1`. ## Hard Rules @@ -28,7 +27,7 @@ Do not use semantic version tags such as `v1.0.0`. 4. Verify no private API key or SSH private key is present in tracked files. 5. Commit the changed source and EXE. 6. Ask the project owner to approve the next version number. -7. Create the next simple tag, for example `v3`. +7. Create the next approved simple tag. 8. Push `main` and the approved tag. 9. If needed, create or update the GitLab Release page for that exact tag.