Skip to content

Removed opinionated statement regarding SemVer (Fix #2132) #2133

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Feb 26, 2020
Merged

Removed opinionated statement regarding SemVer (Fix #2132) #2133

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
8a1c9f3
Removed opinionated statement regard SemVer
jwdonahue Feb 24, 2020
c3b517b
Merge branch 'master' into patch-1
asbjornu Feb 25, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 1 addition & 3 deletions docs/input/docs/more-info/version-increments.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,9 +16,7 @@ version only increases after you release, this directly conflicts with the
concept of published CI builds. When you release the next version of your
library/app/website/whatever you should only increment major/minor or patch then
reset all lower parts to 0, for instance given 1.0.0, the next release should be
either `2.0.0`, `1.1.0` or `1.0.1`. Bumping one of the version components by
more than 1 in a single release means you will have gaps in your version number,
which defeats the purpose of SemVer.
either `2.0.0`, `1.1.0` or `1.0.1`.

Because of this, GitVersion works out what the next SemVer of your app is on
each commit. When you are ready to release you simply deploy the latest built
Expand Down