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
0
votes
1 answer

Can gradle-release-plugin be configured to use SemVer?

I have a Spring-Boot Gradle 4.10.3 project which is currently working fine. It uses gradle-release plugin for releases and version management. However, I now have a new requirement that the artifacts generated for this project adhere to SemVer…
JCN
  • 509
  • 1
  • 11
  • 25
0
votes
1 answer

find if a semantic version is superset of of another version python

I have a use case where I have a list of Java maven semantic ranges trying to find the list of versions that I can exclude in my application. Example: SemVersion1 = "[,1.8.8.1)" SemVersion2 = "[,1.8.8.2)" SemVersion3 = "[,1.8.8.3)" SemVersion4 =…
Jau L
  • 904
  • 2
  • 8
  • 20
0
votes
2 answers

How do I build gitlab-ci pages only on the latest semver tag? Ignoring backport tags/etc

I want to run the gitlab-ci pages job only if the project is getting a new tag pushed. I already know that you can do this with: only: - tags but the issue is that, if we ever push a tag for an older version (a backported bugfix or something)…
DJ SymBiotiX
  • 187
  • 2
  • 12
0
votes
1 answer

Installing package with "@latest" removes semantic versioning

If I am installing a package using the @latest option the semantic versioning found for this package in the package.json is removed. I have removed the package-lock.json file and the node_modules folder before doing the installation and this is…
Andre Oliveira
  • 128
  • 2
  • 12
0
votes
1 answer

Why does this `npm version` command break?

Quite simply, this command works: npm version 0.13.0-20190723T144221.855f01d But this one doesn't: npm version 0.13.0-20190723T125957.0665893 Why? It broke our build process, so it would be useful to understand why this occurred.
Chris Paton
  • 5,113
  • 4
  • 41
  • 52
0
votes
0 answers

Gitflow, artifact versions and pull requests

We are using a variation of gitflow as our branching strategy. A project is initialized with the master branch with the artifact version (in pom.xml, we're using maven) set to 0.0.0 and a dev branch is where the version is updated to the snapshot…
lalli
  • 6,083
  • 7
  • 42
  • 55
0
votes
2 answers

Read assembly version of class library Project from .netCore web app project

I have 4 web applications based on .net core. all of them call a business logic layer (class library) i want my version to get updated on all 4 web applications. I have tried to make a static class on my business logic layer. and on this class i…
0
votes
1 answer

When should I bump dependency version in package.json?

I have a project (called ingester), it has a dependency called sdk. Currently sdk is specified as ^1.30.0 in package.json, in yarn.lock it's resolved as 1.72.0. I released a new version of sdk (1.73.0) and in ingester I explicitly use new stuff…
0
votes
1 answer

NPM release module not detecting git repository

When I am running "release pre beta" on root project. existing project support mono repo structure. It gives me below error. But actually I have the .git folder on my root. [before-after-hook]: "Hook()" repurposing warning, use "Hook.Collection()".…
0
votes
1 answer

Set minimum patch version

Using semver as the standard, so I have this package version: 0.0.108 so in package.json for a Node.js project, I might have something like: "foo":"^0.0.108" my question is - using semver notation, how can I tell NPM not to install anything below…
Alexander Mills
  • 90,741
  • 139
  • 482
  • 817
0
votes
1 answer

Is it correсt to name such versioning a semver?

Good day, fellows. System architect and some developers from my company have said, that to use: For minor version - the number of merge requests For patch - the number of commits is the semantic versioning. I have read the semver spec and I can't…
0
votes
1 answer

How should inter-related software packages be versioned?

Some open-source projects make combined releases where the version number of each package(library) is increased to the same version. Examples in Java are: org.springframework com.fasterxml.jackson org.hamcrest This implies that some packages may…
tkruse
  • 10,222
  • 7
  • 53
  • 80
0
votes
1 answer

NPM semver resolution

I’m brand new to npm, and I need to get list of all possible versions for specified package and semver. Similar that npm semver calculator is doing. For ex.: with entry data: package: tape, semver:’~2.10.1’, result should be:[ 2.10.1, 2.10.2,…
Sveta
  • 1
  • 1
0
votes
1 answer

Is Server canonical for NPM?

Which of these package version numbers is canonical for NPM? 2.0.0-pre1 2.0.0-pre.1
William Entriken
  • 37,208
  • 23
  • 149
  • 195
0
votes
2 answers

Nuget Package Versioning - Max Integer for Major/Minor/Patch?

Is there an upper limit to the major/minor/patch components of a Nuget package version? For instance, can I create MyPackage.1.99999.99999 and upload to Artifactory or Nuget.org and clients will have no issues referencing the package?
user2966445
  • 1,267
  • 16
  • 39