Clean release version references

This commit is contained in:
aseimel
2026-06-30 00:02:00 +02:00
parent 6bc779d0b0
commit fb9bbce9eb
+5 -6
View File
@@ -3,13 +3,12 @@
This project uses simple internal release tags: This project uses simple internal release tags:
```text ```text
v1 v<number>
v2
v3
...
``` ```
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 ## 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. 4. Verify no private API key or SSH private key is present in tracked files.
5. Commit the changed source and EXE. 5. Commit the changed source and EXE.
6. Ask the project owner to approve the next version number. 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. 8. Push `main` and the approved tag.
9. If needed, create or update the GitLab Release page for that exact tag. 9. If needed, create or update the GitLab Release page for that exact tag.