mirror of
https://github.com/semver/semver.git
synced 2026-07-11 03:53:53 -05:00
[GH-ISSUE #868] Working draft version of the website? #6551
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/semver#6551
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 @JohnTitor on GitHub (Aug 13, 2022).
Original GitHub issue: https://github.com/semver/semver/issues/868
Currently, every change here is published every day by GHA workflow: https://github.com/semver/semver.org/blob/gh-pages/.github/workflows/sync.yml
But it means every change needs to bump up the semver's version (NB: we currently don't though), even a change fixes just a small typo, otherwise, it makes a difference between the tagged version and the published version on the website. And it'd also be confusing to have specifications published under the same version but showing different content from day to day (related: https://github.com/semver/semver/issues/799).
Maybe it's better to have a working draft version of the website (e.g. draft.semver.org) and do versioning precisely?
(This issue talks about the website, but it's also related to the semver's versioning, so I'm going to open it here.)
/cc #604, #783
@steveklabnik commented on GitHub (Aug 22, 2022):
Some sort of "latest" version seems prudent, yeah.
@jwdonahue commented on GitHub (Sep 16, 2022):
Perennial complaint. The published spec does not adhere to SemVer versioning. I think the working draft was reflected in the readme.md file for a long time, while the official site content was being generated in the other repo, and that caused some consternation due to them both having the same version number and different content.
The version should not be bumped simply because some automation republishes the content, but it should get bumped for all content changes. Adding new translations, FAQ's, etc., should always be a minor bump. Changes to the spec that make it more clear, with modifying the versioning semantics should be patch level bumps.
@harshking2626 commented on GitHub (Mar 1, 2026):
Hi all my id name harshoproblox I am from india
They all make sure play this game I will do admin abuse at all 7 pm in night