Skip to main content

Questions tagged [semantic-versioning]

De-facto standard for using multi-part version numbers like {major}.{minor}.{patch-level} followed optionally by pre-release labels.

Filter by
Sorted by
Tagged with
1 vote
2 answers
229 views

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 ...
DevQt's user avatar
  • 131
2 votes
2 answers
264 views

Semantic versioning is a scheme of versioning that make the compatibility of different versions of a software component apparent to human and non-human agents. In essence, when a backwards-compatible ...
DannyNiu's user avatar
  • 374
4 votes
5 answers
626 views

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 ...
BadIdeaException's user avatar
0 votes
4 answers
296 views

Suppose I have an application with version 1.2.3. If I refactor my application to remove deprecated calls while maintaining the same functionality and API as in version 1.2.3, what version number ...
Rafael's user avatar
  • 19
0 votes
0 answers
42 views

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 ...
Ala Eddine Menai's user avatar
9 votes
3 answers
7k views

I recently started using Semantic Versioning. Due to conflicts with my previous versioning convention (which I created myself), I am very confused about versioning unit tests as part of the public API....
KhodeNima's user avatar
  • 225
-2 votes
1 answer
1k views

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, ...
jav's user avatar
  • 113
0 votes
3 answers
589 views

I know that it is common for software to have parallel development in major versions, such as v1 (1.x.x), which can be completely different from v2. Regarding Semver (Semantic Version), can I upgrade ...
lvf23's user avatar
  • 47
2 votes
2 answers
2k views

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 ...
F-H's user avatar
  • 131
4 votes
2 answers
3k views

I want my projects to be SemVer compliant. I follow a trunk-based development approach. I also want to keep things as simple as possible. I assume that each commit on main (default branch) is a ...
ebosi's user avatar
  • 149
0 votes
1 answer
386 views

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 ...
JMU's user avatar
  • 9
1 vote
4 answers
989 views

Currently, my repo contains application code and what I call non-functional files, which include deployment scripts, README file, build system requirements, dependencies etc. These files are released ...
tera_789's user avatar
  • 263
-2 votes
2 answers
768 views

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 ...
Kyle Vassella's user avatar
5 votes
1 answer
318 views

I'm in the mobile development domain and I use semantic versioning to version my releases. I keep both versions the same as long as new builds are released for both iOS and Android platforms at the ...
Isuru's user avatar
  • 381
12 votes
4 answers
4k views

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. ...
user2218154's user avatar
0 votes
6 answers
543 views

Semver specifies to update the major version on a backwards incompatible change. Would modifying the behavior for the hash function of a custom type fall under this category? I asked a couple friends, ...
Calvin Godfrey's user avatar
17 votes
2 answers
5k views

All too often, I see people people pointing out flaws in Semantic Versioning (SemVer), or pointing out that it doesn't apply to huge categories of software. (See quotes below). In particular, SemVer ...
David Cary's user avatar
  • 1,492
18 votes
5 answers
4k views

I have a program that runs on command-line, let's call it myprogram 1.0.1. It's published on GitHub. Now I discovered that name already exist for a well-know software, so I want to change the name ...
Lawrence's user avatar
  • 309
4 votes
3 answers
3k views

There are a few threads about how to handle the version number with semver upon changes in dependencies (usually resulting in a +1 to the patch number). Mine is probably a corner case: what if you are ...
floatingpurr's user avatar
3 votes
1 answer
533 views

For the purposes of this question it will be assumed that the conventional commits spec is used as a version driver for semantic versioning. Given a project is in active development. Releases are ...
GDF's user avatar
  • 39
4 votes
2 answers
2k views

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 ...
Rsge's user avatar
  • 61
0 votes
1 answer
1k views

Goal I'm working on libraries published as nuget packages and I would like the version of those packages to update automatically based on the changes I make. In other words, I would like something ...
Batesias's user avatar
  • 274
1 vote
2 answers
817 views

I am making a JS library that creates graphs and charts using canvas. I have hosted it on GitHub as a public repository. So after looking at some other related questions, I have figured out two ...
TalinTheDev's user avatar
1 vote
2 answers
2k views

I am building an Angular web application with a RESTful backend. I plan on using semantic versioning to differentiate between different releases. I've already read a bit about how to implement ...
Maurice's user avatar
  • 133
2 votes
2 answers
636 views

I have a service that uses a package which is basically just a wrapper around an ElasticSearch index. I had to update the index as new data is added on a yearly basis. The source of the data needs to ...
TomMP's user avatar
  • 131
-2 votes
1 answer
206 views

I have a Java library which is deployed automatically to Maven central. Right now this library has Java-1.8 target SDK, I want to continue releasing source code with this target and add new target ...
g4s8's user avatar
  • 126
1 vote
1 answer
425 views

I maintain a CSS framework that is versioning with semantic versioning. What changes to a CSS framework are considered major, minor, and patches? Specifically, what is the "API" of a CSS ...
Kyle Pollard's user avatar
  • 127
10 votes
3 answers
4k views

My company uses Major.Minor.Patch.Build for our version numbers. When a new release is started, the Major.Minor.Patch part is set. Then as work is done, the build number goes up until a build is ...
Vaccano's user avatar
  • 4,077
-1 votes
2 answers
1k views

I'm kinda new in versioning. In my scenario, for example, our main project is currently developing in 2.1.0 (develop branch), while the library version remain same as 1.5.0 since nothing change (for ...
Neo's user avatar
  • 17
9 votes
1 answer
4k views

I'm working on a project that uses Semantic Versioning. The commit history can be generalized as: Also, the current version is present in source code (so that the software can use it for various ...
t-mart's user avatar
  • 209
2 votes
3 answers
5k views

I'm reading a book which says: The third number, 719, indicates the build of the assembly. If your company builds its assembly every day, you should increment the build number each day as well. so it ...
amjad's user avatar
  • 139
1 vote
1 answer
849 views

My question relates to semantic versioning (specifically as specified here). Say I have some feature I introduced in version 1.10.0 and then some time later (let's say the project has advanced to ...
tom's user avatar
  • 129
-1 votes
2 answers
111 views

Assuming that we have a project called: "WizardProject". The WizardProject, which currently stands at version 1.x.x, has a mostly Java based stack and active development has been ...
tschaka1904's user avatar
2 votes
1 answer
4k views

I'm using semantic-release to auto find out the next version based on the git commit. It's working fine with creating new version, upload to npm and create new git tag. And semantic-release is ...
Jake Lam's user avatar
  • 159
0 votes
3 answers
180 views

(This question applies to the equivalent code in both Java and PHP) I have a class like this: class Foo { private int $bar; public function __construct(int $bar) { $this->bar = $...
SOFe's user avatar
  • 728
3 votes
3 answers
1k views

I know with NPM caret, tilde and some logical operators can be used to specify version ranges. This post explains a bit on how this works. The problem now is I find it hard to reconcile the use of ...
Finlay Weber's user avatar
0 votes
2 answers
227 views

According to Wikipedia, we talk about stages of development; prealpha alpha beta release candidate stable But, beta also have 2 sub-stages; perpetual beta open/closed beta Now if we were to ...
Keimeno's user avatar
  • 119
0 votes
2 answers
779 views

I am an amateur developper and I deploy my (home oriented) code to containers. This is usually Python and JavaScript. JavaScript, when saving dependencies for a further npm install, will pin the ...
WoJ's user avatar
  • 1,661
3 votes
1 answer
317 views

We are trying to fix our's company versioning of several modules and I'm not sure how to consider Database compatibility when versioning. The same Database is used for a lot of applications and we're ...
Victor Bello's user avatar
7 votes
2 answers
1k views

I have a library (npm package, LIB) which is used by the application code (APP). In a release of APP, multiple features are worked on parallely. Sometimes these features need support from LIB, so the ...
tbking's user avatar
  • 197
1 vote
0 answers
311 views

I am leading a team of developers creating a Java library. We are following the standard Semantic Versioning model. The code is versioned with Git. Artifacts are built and pushed to an artifact ...
J-bob's user avatar
  • 357
1 vote
1 answer
325 views

This is not about the specification of semver itself (which is crystal clear), but rather about the best approach to implement it within a development pipeline when building libraries. TL;DR: who/what ...
sp00m's user avatar
  • 640
25 votes
3 answers
6k views

I am trying to plan a system which validates the compability of different components by comparing their semantic versioning number, especially the major release number (since it indicates API changes ...
Josef's user avatar
  • 387
-1 votes
2 answers
751 views

I'm developing a SaaS application where I'm required to keep track and publish every change in a changelog. I've started to follow a Semantic Versioning approach and also using Continuous Delivery. ...
Diego Jancic's user avatar
3 votes
3 answers
433 views

I maintain a small (tiny!) .NET library. It has a few ill-defined edge cases, which I call out explicitly in the docs. Places, where the "correct" behaviour is not self-evidently well-defined, so I ...
Brondahl's user avatar
  • 137
0 votes
2 answers
180 views

Some widely used libraries are still versioned 0.x, which under semantic versioning, means they might break the API at any time. Examples of such libraries: numba v0.46, 1.2 million downloads on ...
gerrit's user avatar
  • 1,378
2 votes
1 answer
60 views

This is a scenario I have seen: I have a shared library with code that fetches data from an api. Let's call this ApiProvider. Currently this ApiProvider is in version 1.1.1 and is currently pointing ...
Rafael Rozon's user avatar
3 votes
3 answers
2k views

There's a software library / application / framework which currently uses "simple version numbers". So it's currently at (say) version 135 and releases are made in irregular intervals whenever "there'...
Daniel Jour's user avatar
0 votes
1 answer
1k views

Say I have a three PRs going into the next release. Each PR is a bug fix and all have been approved for the next release. If the current version is 2.3.1, should the next version be 2.3.2 (count all ...
colefner's user avatar
  • 135
3 votes
1 answer
1k views

Let's say I'm maintaining a piece of software that I version following the semver spec. I am also maintaining a docker image for said software, tagged with version tags. What do I do if I need to ...
Anders's user avatar
  • 1,361