Stack Overflow
Stack Overflow

Questions tagged [semantic-versioning]

Semantic Versioning is a community-driven version-numbering standard. Use this tag to indicate the software versioning concepts defined at http://semver.org.

Semantic Versioning is a conceptual software scheme which defines concepts of API compatibility and a specific, strict set of versioning rules intended to avoid dependency hell.

A number of software packages have made a commitment to apply the concepts of Semantic Versioning, or help to enforce its rules. For example: , and other package managers often help manage software dependencies using these rules.

Not all software versioning applies these semantics, which can lead to confusion. Semantic Versioning 2.0.0, the current specification, was originally written by Tom Preston-Werner, and is a community based effort hosted at https://github.com/semver/semver.

664 questions
9
votes
2 answers

Semantic Versioning and Dependency Changes

Some context: I'm working on a team which produces 6 different NuGet packages, which depend directly, and sometimes indirectly, on each other. Simply, we could have a situation like p0 < p1 < p2, where package p0 depends on p1, which in turn depends…
Daniel Miller
  • 287
  • 4
  • 12
9
votes
1 answer

How to version front-end projects?

Semantic versioning brings the follow approach: MAJOR version when you make incompatible API changes MINOR version when you add functionality in a backwards-compatible manner PATCH version when you make backwards-compatible bug fixes However a…
Luan Kevin Ferreira
  • 1,184
  • 2
  • 16
  • 40
9
votes
1 answer

Does npm honour newer prerelease versions in semver?

In my app, I have users install dependencies by running npm install -- bog standard behaviour. However, I have one package that changes frequently, and in an effort to not end up with a ridiculously large version number like 0.1.12324, I stumbled…
Julian H. Lam
  • 25,501
  • 13
  • 46
  • 73
8
votes
0 answers

How to automatically bump version of peerDependencies for local packages in a monorepository with yarn worskpaces?

When running lerna version or lerna publish it bumps versions of all the packages in yarn workspace and do update relevant devDependencies but keeps unchanged versions in peerDependencies so packages reference old & incorrect versions and that…
Alexander Trakhimenok
  • 6,019
  • 2
  • 27
  • 52
8
votes
2 answers

GitVersion configuration is not incrementing

I'm trying to setup GitVersion to handle our project's semantic versioning (GitFlow), but it's not incrementing automatically as I'm expecting. I'm also struggling with reading the project's documentation, it's not the easiest to follow. Basically…
Ryan Grush
  • 2,076
  • 3
  • 37
  • 64
8
votes
3 answers

Private NPM: How can the latest version of a module be installed?

Using private npm, common commands seem not to work: npm install without a specific @version :: issue npm outdated :: issue npm update :: issue npm view versions :: (haven't found issue yet) also note that npm v, npm show,…
1252748
  • 14,597
  • 32
  • 109
  • 229
8
votes
1 answer

Indermediate sub-patch Node.js package version

I'm providing accompanying package that matches the version of the main NPM package, already in major.minor.patch format (e.g. 1.3.1). I don't want to break version conformity between main and accompanying package. Is it possible to release…
Estus Flask
  • 206,104
  • 70
  • 425
  • 565
8
votes
1 answer

npm - release module multiple branches with multiple versions

I have a npm module which is already released under 4.x.x version and have breaking changes comparing to 3.x.x stable version. However I have some updates to 3.x.x version and want to patch its' npm version. Is it possible? Can I manage 2 major…
Kosmetika
  • 20,774
  • 37
  • 108
  • 172
8
votes
1 answer

In Dart with Pub, when should I use the "any" version constraint for a dependency?

When making a package, I am often confused as to whether I should use the any constraint. I know that for: library packages, I should specify clear version constraints so that users of my libraries know the version of my transitive…
Juniper Belmont
  • 3,296
  • 2
  • 18
  • 28
7
votes
2 answers

Error: Compiler version ^0.8.0 does not satisfy the r semver requirement

I am new to solidity and I am running code on Remix. It doesn't matter what version of compiler I specify, I keep on getting the same error. Can someone help me out? What does "Compiler version ^0.8.0 does not satisfy the r semver requirement"…
김예군
  • 169
  • 2
  • 7
7
votes
2 answers

How to use npm version to increment the counter behind the prepatch / preid suffix

I'm trying to find out how to correctly use npm version with prepatch (also premajor or preminor) / preid options to increment the counter behind the suffix. e.g.: I have a v.0.5.22 and want to append -rc I used the command npm version prepatch…
Sascha
  • 858
  • 1
  • 16
  • 30
7
votes
4 answers

How to setup semantic-release without the need for npm?

I have a C# project and would like to add semantic versioning to it. So whenever I push to the main branch I want to create a new release and autogenerate a new version number based on the commit types. I think semantic-release does the job very…
Question3r
  • 2,166
  • 19
  • 100
  • 200
7
votes
1 answer

How to ensure Master and Dev branches are kept in sync when deploying from CI/CD with Semantic Versioning or Lerna Publish

Setup I have several gitlab repos where the general setup involves having a master branch, a stage (pre-release) branch and a dev branch. Push permissions are disabled for all 3 branches. The workflow is to fork from the dev branch for any…
Daniel Mastrorillo
  • 151
  • 11
7
votes
1 answer

What does OR operator mean in package.json for an npm package's version?

What is the significance of OR operator (||) between npm versions? Eg: "dependencies": { "@jupyter-widgets/base": "^1.1.10 || ^2 || ^3" } I see version 3 is always installed for me.
Anant_Kumar
  • 764
  • 1
  • 7
  • 23
7
votes
1 answer

Does caret (^) in semver matches pre-release when pre-release version is the latest available version?

Consider having library (e. g. NPM package) with these versions: 1.0.0 1.0.2 1.1.0-prerelease If I specify ^1.0.0 in my dependencies, what will be version that will be installed? 1.1.0-prerelease is the latest version, but I don't think any…
Garret Raziel
  • 375
  • 1
  • 8
  • 20
1 2 3
…
44 45