I wonder how should we manage the commits we make AFTER a version is released, according to SEMVER. For example, I just released 1.0.1, now I have 2 choices:
Immediately change version to 1.0.2 and start working on this version. Once the work is finished, I'll just tag the last commit to be officially the version 1.0.2 (this seems to be the SEMVER-way of doing it).
Continue working on 1.0.1 and then when I finished, I make a commit to change the version to 1.0.2 and tag this last commit as the official version 1.0.2.
Actually, SEMVER tells that
Once a versioned package has been released, the contents of that version MUST NOT be modified. Any modifications MUST be released as a new version.
But the second way seems more logical to me, as when a version is incremented, the software should already have all the functionnalities of this particular version. So what should I do?