mirror of
https://github.com/semver/semver.git
synced 2026-03-22 14:10:15 -05:00
Change log for SemVer 2.0 #91
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/semver#91
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 @mnapoli on GitHub (Jul 22, 2013).
SemVer 2.0 needs a change log. What has fundamentally changed since 1.* version that requires us to change anything?
This is the basics of versioning ;)
@njharman commented on GitHub (Jul 22, 2013):
source control is change log https://github.com/mojombo/semver/compare/v1.0.0...v2.0.0
@mnapoli commented on GitHub (Jul 22, 2013):
You could say that for every existing project, yet most of them provide a change log. Not everybody will take time looking at diffs to see what has changed.
Since there is a major number increment, a visitor can assume there are large, uncompatible changes with v1.0. That's too bad there is no summary of the major change that triggered the new major version.
@andrew-kzoo commented on GitHub (Jul 22, 2013):
I'm glad to see 2.0.0, though also a bit surprised its come without a changelog.
@dwijnand commented on GitHub (Feb 12, 2014):
👍
@creynders commented on GitHub (Feb 25, 2014):
👍
And a commit log is not a change log IMO, it's filled with irrelevant cruft: typo fixes etc. It doesn't provide an overview of what fundamental changes have happened.
@crazedsanity commented on GitHub (Feb 25, 2014):
+1
I totally agree that there should be a change log. Besides being able to understand what's changed, it could also serve as guidance for others as to what constitutes a major version update. Going forward, it would be supremely helpful in determining if a project that was compliant with SemVer 2.0 is in compliance with 3.0.
@andrew-kzoo commented on GitHub (Feb 25, 2014):
a commit log is not a change log👍
I'm glad to see new comments on this issue!
@mkalb commented on GitHub (Feb 26, 2014):
👍
@maximal commented on GitHub (Feb 26, 2014):
+1
@creynders commented on GitHub (Feb 26, 2014):
Just in case, for people who don't know, you can see the rendered diff here on github (not ideal, but better than nothing) Unfortunately I can't refer to it directly, so you need to follow these steps:
Very unintuitively this will bring you back to the 'commits' page, so you need to:
As I said it's not ideal, since it will just show all changes and not the relevant ones, but it does give a bit more information.
@crazedsanity commented on GitHub (Feb 26, 2014):
Well, that is at the least a useful tool to be able to create a change log. Thanks for the tip, @creynders.
@dwijnand commented on GitHub (Feb 26, 2014):
Does this link work?
https://github.com/mojombo/semver/compare/v1.0.0...v2.0.0?name=v2.0.0&path_md5=55782f4#files_bucket
On 26 February 2014 09:33, creynders notifications@github.com wrote:
@crazedsanity commented on GitHub (Feb 26, 2014):
It sure does, @dwijnand, thanks!
@creynders commented on GitHub (Feb 26, 2014):
@dwijnand Ah cool, I tried a dozen different ways to get a url leading to that, but always got thrown back at the main comparison page.
@jwdonahue commented on GitHub (Dec 2, 2017):
@mnapoli, unless you wish to pursue this issue further, please close it at your earliest possible convenience.
@gregmac commented on GitHub (Mar 11, 2023):
So from what I see:
Breaking changes from Semver 1.0.0 to 2.0.0:
Other major changes
2bfa9b0)52c9b2b)84c9618)Diff: Code | Commits