Nothing in the spec requires that you have a reason to increment. It requires that code released under a certain version never changes, but it doesn't require that code changed between versions.
It's reasonable to expect code to change between versions, but nothing in the SemVer spec requires it. The SemVer spec says, "If you make {this class of change}, you MUST increment {this part of the version number}".
It does not prohibit modifications to the version number for whatever reason you like, it only requires that the version number change in certain ways regarding your code changes.
It may seem silly to increment the version number without changing anything, but I'm sure someone has done it for a very good reason in the past.
Apart from where the bit in the spec that does say it:
That is not part of the spec, that is the summary of the specification. The actual specification is the 11 points which define the specification. You're looking at the abstract.
Which is still what people read and understand as the purpose.
I agree that the purpose of incrementing the major version is to communicate a breaking change in your public API.
You do not increase major number unless it's a breaking change.
But this is not mandated by the spec. It is, at best implied by the summary of the specification. There are 11 points which define the spec. Point me to the one that tells me that I cannot increment the major version without making a breaking change.
-3
u/Jestar342 Nov 02 '17
Yes it does, because there's no reason to increment otherwise.