mirror of
https://github.com/semver/semver.git
synced 2026-07-11 06:24:32 -05:00
[GH-ISSUE #235] When should or shouldn't a version number have a 'v' at the beginning? #1026
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/semver#1026
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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.