In SemVer should I increase the version on every commit/accepted pull request
Running a community project. Have a few pull requests that have been made and the version of our product is currently 2.5.0
What kind of version change is updating to a new .NET-version when using SemVer?
When updating to a new major version of .NET (in this case from .NET 5 to .NET 6) without needing to make any change other than selecting the new target framework in Visual Studio, does this warrant a new major or minor version or does bumping the patch version suffice, when adhering to SemVer-principles?
How do I properly apply semantic versioning if I have more than three components in my version?
I am preparing a software package for internal consumption in my organization. It will be published on our internal non-public npm feed.
How to differentiate versioning between changes on version 1.0 and adding new features towards 2.0?
If I met all requirements on version 1.0 and go on working towards version 2.0, new features would be 1.1, 1.2, 1.3, and so on. What do I version the commits that represent an important fix or a forgotten feature which is required in version 1.0? Even if I didn’t version fixes on version 1.0, there would still be two version 1.0.1s until the develop branch merges into the master branch.
Semantic Versioning – going from one major version to another?
How should versions be bumped during development between two major versions?
For example let say I have version 1.5.0 and my target is to release new major version that will be incompatible with major version 1.