Questions tagged [semantic-versioning]
De-facto standard for using multi-part version numbers like {major}.{minor}.{patch-level} followed optionally by pre-release labels.
130 questions
1 vote
2 answers
226 views
Application of Semantic Versioning Specifications Between 1.0.0-alpha and 1.0.0-alpha.1
I have no concrete idea about the main difference between 1.0.0-alpha and 1.0.0-alpha.1 of a system SemVer when it's applied in a real event of the system's development. Can someone explain the ...
- 131
4 votes
5 answers
625 views
Is changing the signature of a callback a breaking change?
In Javascript, should appending to the signature of a callback be considered a breaking change? I.e. given an operation op(target, callback) should changing it from callback(item, index, array) to ...
- 151
0 votes
0 answers
42 views
Should I increment the MAJOR number in Semantic Versioning when I change the flow of the app? [duplicate]
We are developing a web application and we are in the version 1.2.0. In the next release we will change the flow of the app by removing 2 pages and making other pages as Modals and change the user ...
- 245
-2 votes
1 answer
1k views
How to go about version numbers in a C# solution
My current situation: I would like to apply this to a solution containing multiple projects (one executable and different libraries) in C#. Additionally, I have a project that packs the executable, ...
- 113
2 votes
2 answers
2k views
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. The used technology (npm) requires me to adhere to semantic ...
- 131
0 votes
1 answer
385 views
Automatic detection of semantic versioning based on Python type hints
I am the maintainer of a Python library that uses semantic versioning. Skip the next paragraph if you are familiar with what it means. The rough and dirty explanation of semantic versioning is as ...
- 9
-2 votes
2 answers
766 views
What should my next SemVer version number be?
For a frontend web app version 3.9, we have a visual change that I would constitute as a backwards compatible (as far as the API) new feature. Therefor, my SemVer instinct is to bump the minor version ...
- 111
12 votes
4 answers
4k views
Guidance on rectifying a minor bump that should have been a major bump
We have product X which has the following semver versions: 1.0.0, 1.1.0, 1.2.0, ..., 1.10.0. In version 1.5.0, we introduced a feature which changes the way the application is consumed in a big way. ...
- 139