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?
Deploying two major versions of a spring boot java app with the same pod in kubernetes
We have a spring boot java application that is deployed using kubernetes . It mostly runs background jobs. We have two different groups of customers .
The requirement is that when we do a major upgrade (lets say monthly) the software should be rolled out to only one group of customers.The second group gets the same version after a month.
This is primarily because the second group has a different financial closing period and they do not want any instability wrt new code changes.
How to modify workflow to allow multiple features per release?
This question is inspired by comments on this recent question. In that question I asked about a version tagging workflow. A few commenters suggested it was a little strange that I’m tagging and releasing every new feature that is merged into main. It sounds like it is more typically to collect up a few new features and then make a version bump/release. I’m trying to understand how this workflow would look and how I would modify my current workflow.
An elegant way to store build counter [closed]
Closed 6 years ago.
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.