[GH-ISSUE #454] Home page and link to spec v2.0.0 are different #1196

Closed
opened 2026-04-16 10:30:43 -05:00 by GiteaMirror · 4 comments
Owner

Originally created by @Relequestual on GitHub (Aug 3, 2018).
Original GitHub issue: https://github.com/semver/semver/issues/454

The content of https://semver.org/ (which is titled 2.0.0), and the link for 2.0.0 (which is https://semver.org/spec/v2.0.0.html) are different.

The home page has a tiny language bug fix which doesn't effect "functionality", but shouldn't that change, even of a single word, have resulted in a patch version bump?
OR is the assumption that fixing typos / correcting bad words doesn't warrant a patch release?

If I'm referencing 2.0.0 somewhere, I want to use the 2.0.0 link, in case a newer version is released and lands on the home page, right?

Originally created by @Relequestual on GitHub (Aug 3, 2018). Original GitHub issue: https://github.com/semver/semver/issues/454 The content of https://semver.org/ (which is titled 2.0.0), and the link for 2.0.0 (which is https://semver.org/spec/v2.0.0.html) are different. The home page has a tiny language bug fix which doesn't effect "functionality", but shouldn't that change, even of a single word, have resulted in a patch version bump? OR is the assumption that fixing typos / correcting bad words doesn't warrant a patch release? If I'm referencing 2.0.0 somewhere, I want to use the 2.0.0 link, in case a newer version is released and lands on the home page, right?
Author
Owner

@jwdonahue commented on GitHub (Aug 18, 2018):

I think the home page should simply redirect to the v2.0.0.html file. That would eliminate any chances of them ever getting out of sync again. As for the advertised spec version, I think that probably refers to the content of the Semantic Versioning Specification section. But I do agree with you. I think we should have seen some version bumps along the way.

<!-- gh-comment-id:414028305 --> @jwdonahue commented on GitHub (Aug 18, 2018): I think the home page should simply redirect to the v2.0.0.html file. That would eliminate any chances of them ever getting out of sync again. As for the advertised spec version, I think that probably refers to the content of the [Semantic Versioning Specification section](https://semver.org/#semantic-versioning-specification-semver). But I do agree with you. I think we should have seen some version bumps along the way.
Author
Owner

@beruic commented on GitHub (Dec 3, 2018):

I am glad I am not the only one that saw this dreaded discrepancy

<!-- gh-comment-id:443885633 --> @beruic commented on GitHub (Dec 3, 2018): I am glad I am not the only one that saw this dreaded discrepancy
Author
Owner

@steveklabnik commented on GitHub (Feb 11, 2019):

Closing in favor of https://github.com/semver/semver/issues/407 which is older. Thanks!

<!-- gh-comment-id:462475887 --> @steveklabnik commented on GitHub (Feb 11, 2019): Closing in favor of https://github.com/semver/semver/issues/407 which is older. Thanks!
Author
Owner

@Relequestual commented on GitHub (Feb 27, 2019):

@steveklabnik But that issue includes the markdown file in the repo too, which has been noted is "development", which is fine.

<!-- gh-comment-id:467884836 --> @Relequestual commented on GitHub (Feb 27, 2019): @steveklabnik But that issue includes the markdown file in the repo too, which has been noted is "development", which is fine.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/semver#1196