Home » Community » U++ community news and announcements » GIT release tag naming convention has been changed
| GIT release tag naming convention has been changed [message #61766] |
Sun, 03 August 2025 21:17  |
 |
Klugier
Messages: 1106
Registered: September 2012
Location: Poland, Kraków
|
Senior Contributor |
|
|
Hello,
I would like to inform you that I decided to change the naming convention for version tags in our main repository. So, instead of having "2025.1.1", now we have "v2025.1.1". This notation is de facto standard for versions naming convention on git. Other significant projects such as Linux kernel are using it.
Also, with this change links to the releases changed, so if your script is basing on GitHub artifacts it is highly recommended to updated them. Here is the example:
https://github.com/ultimatepp/ultimatepp/releases/tag/v2025.1.1 // <- New
https://github.com/ultimatepp/ultimatepp/releases/tag/2025.1.1 // <- Old (lack of v prefix in version part)
Klugier
U++ - one framework to rule them all.
|
|
|
|
| Re: GIT release tag naming convention has been changed [message #61767 is a reply to message #61766] |
Mon, 04 August 2025 09:46  |
Oblivion
Messages: 1223
Registered: August 2007
|
Senior Contributor |
|
|
Hello Klugier,
Is this really necessary?
I mean, I already updated my scripts, no big problem for me, but this change can break many projects we're (NOT) aware of, for no real reason.
Yes, linux and coreutils use a similar scheme, but other major players (e.g. Microsoft, LLVM, etc.) don't. Besides, in github "tag" usually means release version.
Best regards,
Oblivion
Github page: https://github.com/ismail-yilmaz
Bobcat the terminal emulator: https://github.com/ismail-yilmaz/Bobcat
[Updated on: Mon, 04 August 2025 09:47] Report message to a moderator |
|
|
|
Goto Forum:
Current Time: Mon Aug 11 23:32:26 CEST 2025
Total time taken to generate the page: 0.05477 seconds
|
Members
Pages
Help
Register
Login
Home
