At the top of the document all the version have a 'v' character in the front. I'm curious why this is, when it should and shouldn't occur.
v2.0.0 v2.0.0-rc.2 v2.0.0-rc.1 v1.0.0 v1.0.0-beta
It's a weird appearance that isn't mentioned anywhere in the documented. If I have a list of version and some of them have the v in front and some don't it will be some odd inconsistencies when it comes to sorting. Thoughts/Comments?
Originally created by @RyPeck on GitHub (Dec 2, 2014).
Original GitHub issue: https://github.com/semver/semver/issues/235
At the top of the document all the version have a 'v' character in the front. I'm curious why this is, when it should and shouldn't occur.
```
v2.0.0 v2.0.0-rc.2 v2.0.0-rc.1 v1.0.0 v1.0.0-beta
```
It's a weird appearance that isn't mentioned anywhere in the documented. If I have a list of version and some of them have the v in front and some don't it will be some odd inconsistencies when it comes to sorting. Thoughts/Comments?
In my opinion the leading 'v' belongs to a tag (e.g. on a git repo) but does not belong to the version string itself. Also in #232 the leading 'v' is not found by the suggested regular expression to check for a semantic version string. And also #234 proposes a fix.
<!-- gh-comment-id:65201884 -->
@tbeu commented on GitHub (Dec 2, 2014):
In my opinion the leading 'v' belongs to a tag (e.g. on a git repo) but does not belong to the version string itself. Also in #232 the leading 'v' is not found by the suggested regular expression to check for a semantic version string. And also #234 proposes a fix.
semver version numbers must not include redundant information such as a 'v' prefix. For git tags this is ok as it is a common best practice.
What is it with you people wanting to introduce such redundancies in the most simple of things?
e.g.
v1.0.0.304.455
1.0.0-build-459485-rc-1
and so on.
KISS is the main principle here.
And clean up your processes.
<!-- gh-comment-id:346477428 -->
@silkentrance commented on GitHub (Nov 22, 2017):
semver version numbers must not include redundant information such as a 'v' prefix. For git tags this is ok as it is a common best practice.
What is it with you people wanting to introduce such redundancies in the most simple of things?
e.g.
```
v1.0.0.304.455
1.0.0-build-459485-rc-1
```
and so on.
KISS is the main principle here.
And clean up your processes.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @RyPeck on GitHub (Dec 2, 2014).
Original GitHub issue: https://github.com/semver/semver/issues/235
At the top of the document all the version have a 'v' character in the front. I'm curious why this is, when it should and shouldn't occur.
It's a weird appearance that isn't mentioned anywhere in the documented. If I have a list of version and some of them have the v in front and some don't it will be some odd inconsistencies when it comes to sorting. Thoughts/Comments?
@tbeu commented on GitHub (Dec 2, 2014):
In my opinion the leading 'v' belongs to a tag (e.g. on a git repo) but does not belong to the version string itself. Also in #232 the leading 'v' is not found by the suggested regular expression to check for a semantic version string. And also #234 proposes a fix.
@silkentrance commented on GitHub (Nov 22, 2017):
semver version numbers must not include redundant information such as a 'v' prefix. For git tags this is ok as it is a common best practice.
What is it with you people wanting to introduce such redundancies in the most simple of things?
e.g.
and so on.
KISS is the main principle here.
And clean up your processes.
@steveklabnik commented on GitHub (Feb 11, 2019):
The
vhas since been removed. Closing!@bcope commented on GitHub (Sep 13, 2022):
Link to SemVer documentation that specifies this.