[GH-ISSUE #783] Tags in this repo are not up to date #5633

New Issue

GiteaMirror · 2026-06-15T12:09:02-05:00

GiteaMirror commented

2026-06-15 12:09:02 -05:00

Originally created by @JC3 on GitHub (Dec 9, 2021).
Original GitHub issue: https://github.com/semver/semver/issues/783

The tags in this repo do not seem to correspond to the published version of the spec.

For example, the published version of 2.0.0 does not match the tagged version v2.0.0. On a cursory diff, there appear to be a large number of differences.

I'm not entirely certain which commit in this repo corresponds to the currently published standard.

Tbh... it is a bit odd considering that versioning is precisely the topic of this spec, but... 😅

The tags (or releases would work too -- currently there are none) here really ought to be updated to match published versions, and then maintained in future updates.

Originally created by @JC3 on GitHub (Dec 9, 2021). Original GitHub issue: https://github.com/semver/semver/issues/783 The [tags in this repo](https://github.com/semver/semver/tags) do not seem to correspond to the published version of the spec. For example, the [published version of 2.0.0](https://semver.org/spec/v2.0.0.html) does not match the [tagged version v2.0.0](https://github.com/JC3/semver/blob/v2.0.0/semver.md). On a cursory diff, there appear to be a large number of differences. I'm not entirely certain which commit in this repo corresponds to the currently published standard. Tbh... it is a bit odd considering that versioning is precisely the topic of this spec, but... 😅 The tags (or releases would work too -- currently there are none) here really ought to be updated to match published versions, and then maintained in future updates.

GiteaMirror commented

2026-06-15 12:09:04 -05:00

@jwdonahue commented on GitHub (Dec 12, 2021):

The maintainers have never applied the spec's semantics to its own version. There have been many 2.0.0 publications over the years. Past maintainers have pointed to other standards bodies that have allowed minor updates to be taken without bumping the version as an excuse. I would guess that we're on something like 2.>3.>10, but I haven't done the spelunking to determine exactly where we should be.

Repo tags are useless in all but the most regulated environments and even then suspect. But the version number included in the title of the spec, that's something that's immutable w.r.t. the repo hash. The web site should emit that hash, and the title should contain the SemVer appropriate version for that release.

I and others have already lost that argument in the past. Pretty sure you'll find at least a handful of threads on the topic if you search for them.

@jwdonahue commented on GitHub (Dec 12, 2021): The maintainers have never applied the spec's semantics to its own version. There have been many 2.0.0 publications over the years. Past maintainers have pointed to other standards bodies that have allowed minor updates to be taken without bumping the version as an excuse. I would guess that we're on something like 2.>3.>10, but I haven't done the spelunking to determine exactly where we should be. Repo tags are useless in all but the most regulated environments and even then suspect. But the version number included in the title of the spec, that's something that's immutable w.r.t. the repo hash. The web site should emit that hash, and the title should contain the SemVer appropriate version for that release. I and others have already lost that argument in the past. Pretty sure you'll find at least a handful of threads on the topic if you search for them.

GiteaMirror commented

2026-06-15 12:09:04 -05:00

@jwdonahue commented on GitHub (Dec 12, 2021):

Oh, I would add that the website is generated from the other repo at https://github.com/semver/semver.org where all of the website content is generated, including the translations.

@jwdonahue commented on GitHub (Dec 12, 2021): Oh, I would add that the website is generated from the other repo at https://github.com/semver/semver.org where all of the website content is generated, including the translations.

GiteaMirror commented

2026-06-15 12:09:04 -05:00

@JC3 commented on GitHub (Dec 12, 2021):

Bleh. Well it is what it is. It's not a huge deal that versions aren't bumper on changes I guess (although then parser implementors are less aware of updates), but I think at least the tag should match the website.

Maybe the best compromise is to just move the current v2.0.0 tag to the current revision so it matches the actual published spec?

@JC3 commented on GitHub (Dec 12, 2021): Bleh. Well it is what it is. It's not a huge deal that versions aren't bumper on changes I guess (although then parser implementors are less aware of updates), but I think at least the tag should match the website. Maybe the best compromise is to just move the current v2.0.0 tag to the current revision so it matches the actual published spec?

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/semver#5633