Questions tagged [semantic-versioning]
De-facto standard for using multi-part version numbers like {major}.{minor}.{patch-level} followed optionally by pre-release labels.
106
questions
-2
votes
1answer
68 views
Version naming for source code with multiple build targets
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 ...
1
vote
1answer
86 views
Semantic Versioning for CSS
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 ...
1
vote
3answers
194 views
How to deal with SemVer in a build number based company
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 ...
-1
votes
2answers
136 views
How to version bug fix of library for earlier release?
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 ...
1
vote
1answer
86 views
Which SemVer version to use between releases?
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 ...
1
vote
3answers
554 views
When to increment build number?
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 ...
0
votes
0answers
8 views
Communicate compatibility using a synchronized versioning scheme
Context
Suppose I want to create a library A that consumes the API of third party semversioned software B. The audience of library A is expected to use B. What would be considered a good practice for ...
1
vote
1answer
61 views
How do deal with bugs in semantic versioning introduced in old branches
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 ...
-1
votes
2answers
89 views
Versioning of re-implementation - same idea, same name, new project and repo - 1.0.0 or 2.0.0?
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 ...
1
vote
1answer
1k views
What's the best practice to use semantic-release to update version number in a node.js or frontend project
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 ...
0
votes
3answers
147 views
Should it be considered a BC break to return clone instead of new self?
(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 = $...
2
votes
3answers
352 views
How is a reproducible build guaranteed with version ranges in NPM?
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 ...
0
votes
2answers
136 views
What can be used as abbreviation for perpetual beta?
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 ...
-1
votes
2answers
170 views
Why are minor versions of dependencies pinned, despite possibly having bugs?
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 ...
3
votes
1answer
174 views
Projects version and database compatibility
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 ...
6
votes
2answers
537 views
Versioning in parallel features development
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 ...
1
vote
0answers
105 views
Gradle + Git - enforcing a version change upon merge to master
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 ...
1
vote
1answer
129 views
Implementing semver within a development pipeline when building libraries
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/...
24
votes
3answers
3k views
How to change the semantic version number when reverting the last major change
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 ...
-1
votes
2answers
341 views
Git Tagging for SaaS application with CD and SemVer
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.
...
3
votes
3answers
243 views
In SemVer, am I allowed to change the in-practice behaviour of undefined behaviour usages
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 ...
0
votes
2answers
126 views
Can a library reach v1.0 when its dependencies haven't?
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 ...
2
votes
1answer
42 views
Should I update the major version of a consumer package if one of its critical dependencies has a major update?
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 ...
2
votes
3answers
641 views
Switching to semantic versioning from simple version numbers
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'...
-1
votes
1answer
258 views
Proper version incrementation with multiple bug fixes in same release
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 ...
2
votes
1answer
171 views
How to handle patch version bumps for docker images when the software itself is unchanged?
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 ...
0
votes
1answer
126 views
How far to go with semantic versioning?
Say you have an interface with a function List<A> doSomething(Collection<B> bs). Looking at Java's List interface and its JavaDoc I could return an immutable List which doesn't support ...
0
votes
1answer
243 views
How does a software engineer version two minor updates at the same time?
In a web app I am building, I might finish two distinct minor features at the same time: Implementation of a new web page, and implementation of the notification bar. After merging both of these into ...
0
votes
1answer
1k views
Microservices Versioning - Design Pattern
I have a few questions regarding the versioning in the microservices architecture:
Let's say there are three services - S1, S2, S3
S1 calls S2 and S3 to generate a response R1.
Service S2 generates ...
3
votes
1answer
674 views
Is it okay to use a patch version in semver when updating documentation?
How does one go about e.g. missing documentation in the source files when using semver? I have just released 1.0 of my library and noticed that a class is missing JavaDoc - is it ok to release a PATCH ...
0
votes
1answer
164 views
Change semver versioning after dropping node eninge versions
I doubt about to which semver version I should update my public NPM package. I didn't change any code, but I had to drop some node engine versions due to a dependency package which had a major update ...
2
votes
2answers
145 views
How to manage updates after a release?
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 ...
2
votes
1answer
669 views
Using semantic version with trunk based development for Python package
I am trying to understand trunk based development with semantic versioning for a Python project. Has anyone had any experience of adopting a trunk based development with semantic versioning for ...
3
votes
1answer
222 views
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 ...
4
votes
1answer
625 views
What would be the pros and cons of requiring major versions to be forward compatible? [closed]
So I was learning about forward compatibility, and I was wondering if you could warn a "dependent" that a dependency is backward compatible, but not forward compatible*, and vice-versa.
The SemVer ...
32
votes
4answers
6k views
When should a commit not be version tagged?
Context: I recently found out about Semantic Versioning, and am trying to determine how to best use it practically for my own projects.
Given that semver takes major changes, minor changes, and ...
-1
votes
1answer
301 views
How to use Semantic Versioning on Existing Multi Component Codebase?
I am working on a multi contributor project, having ~2500 Commits. It has multiple components, i.e. Frontend, Backend and Data Processor/DB Ingestion.
Now that we are expecting more contributors, a ...
7
votes
2answers
224 views
Semantic Versioning
If a change compiled/built but the semantics were different would it be considered a major change?
For example, suppose a time string returned was the same format but now was CET rather than, say, ...
1
vote
2answers
102 views
How to update version when only dependencies are updated?
I have a public project that I'm the single developer. I love updating packages to new versions regularly and keep the project up to date with the updated environment. This is probably not always a ...
1
vote
3answers
182 views
Versioning different flavors built from shared source
I need advice on how to version builds based on shared and separate codes at the same time. I have a gradle project with multiple flavors. Large part of the code is shared. Some parts are flavor ...
7
votes
2answers
6k views
What is a predictable versioning strategy for a monorepo using semver?
To simplify deployment and project management tasks I maintain a monorepo containing several packages that each have a semver version. To be clear, I don't mean several repositories managed from one ...
10
votes
2answers
4k views
Using Gitflow and Semantic Versioning: How to avoid version number conflicts when merging?
I want to use gitflow in combination with semantic versioning. In gitflow, you bump version numbers on every release or hotfix branch. This inevitably leads to version conflicts if a new development ...
0
votes
2answers
1k views
Semantic versioning for content websites
How applicable is it to adapt SemVer for content-centric websites (ie/ not web apps)?
Most of the SemVer 2.0.0 specifications able to translate into such type of websites however it becomes vagues ...
4
votes
1answer
144 views
Dependency management for facades/adapters to cloud services (SemVer?)
Suppose I have a library, that basically works as a facade to some cloud service (e.g. JavaScript API that wraps around network calls to some RESTfull service). And once that service introduces a ...
2
votes
1answer
207 views
Version number for multiple softwares coming from same code base
We currently have a big code base from which we can generate 5 differents softwares.
The code base is composed of around 20 submodules which are used (or not) by each software.
Keeping a semver for ...
5
votes
3answers
399 views
Best practices on sharing code between open source libraries
I have an Android library used by a decent amount of people, let's call it library A.
I am building a second library, library B.
The two libraries are conceptually related, they solve different ...
-1
votes
1answer
300 views
Multi module project version management
I have a CMake multi module project made of a library and an executable. Both the root project and each sub module has its own version (major.minor.patch).
I would like to know how to handle each ...
8
votes
3answers
4k views
Is a breaking change bug fix a semver patch or a major?
Your package has a bug. Its API in some scenarios doesn’t follow the documentation and the intended behaviour. It has been that way since it was v1.0.0. You fix it to match the documentation. Should ...
0
votes
2answers
860 views
What should be the version of the very first build of a software? [closed]
As the title explains the question, let's assume that we're using versioning as major.minor.revision.build. What should the initial version of a software build be? 0.0.0.1 or 0.0.0.0 or anything else?
1
vote
2answers
167 views
Should each new feature for an open source project have a new minor version?
I develop an open-source project. According to this webpage, you should increment the "MINOR version when you add functionality in a backwards-compatible manner".
Suppose I'm developing two distinct ...
