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

Possible to use R.__ with semver functions?

const semvers = ["5.100.0-rc.0", "5.97.3", "5.97.1"]; const newRecord = "5.97.2"; Given the above test data, I wish to insert newRecord into the right order, defined/sorted by semver package. result = ["5.100.0-rc.0", "5.97.3", "5.97.2",…
Isaac
  • 12,042
  • 16
  • 52
  • 116
0
votes
0 answers

git flow tags - what's the sequence

From the specification https://semver.org/, the tag sequence is (I did adjust for my question) 1.0.0 < 1.0.1-alpha < 1.0.1-alpha.1 < 1.0.1-alpha.beta < 1.0.1-beta < 1.0.1-beta.2 < 1.0.1-beta.11 < 1.0.1-rc.1 < 1.0.1 But my company wants to use this…
Bill
  • 2,494
  • 5
  • 26
  • 61
0
votes
1 answer

How to upgrade version number for previous release with semantic-release

Currently, I have a package with currnet version 2.0.1, i want to release fix for previous version i.e v1.0.1, how to achieve this in github, should i checkout to v1.0.1 branch and then create fix and merge it to master ? Are there any steps which…
Akash Salunkhe
  • 2,698
  • 2
  • 16
  • 31
0
votes
1 answer

Different packageRules for release and prelease versions

Is there a way to configure renovate with packageRules, so that I get a MR with automerge disables for pre-release versions, like v1.0.0-alpha.1 and MR with automerge enabled for patch versions, liken v1.0.0. I have enabled unstableVersion support…
Jehof
  • 34,674
  • 10
  • 123
  • 155
0
votes
0 answers

Using OpenAPI Spec for Semantic Versioning Releases

I am deploying a FastAPI application to docker and I'm pondering how to best manage the Semantic Versioning. Since it is just an API, I would think that MAJOR.MINOR.PATCH could be determined by comparing the previous builds OpenAPI Spec to the…
Kenton Parton
  • 70
  • 1
  • 5
0
votes
1 answer

Handling hotfix in gitversion

I'm trying to understand how GitVersion works. Here there is a snippet for 'gitversion /showconfig' branches: develop: mode: ContinuousDeployment main: mode: ContinuousDelivery hotfix: mode: ContinuousDelivery ... After shipping…
Riccardo79
  • 954
  • 4
  • 17
  • 35
0
votes
0 answers

From node-semver documentation, what is meaning of symbol "-0" after version

~1.2.3 := >=1.2.3 <1.(2+1).0 := >=1.2.3 <1.3.0-0 (highlighted) In above example, what is the meaning of symbol -0 after version(1.3.0-0)? see: https://github.com/npm/node-semver#versions
coldMater
  • 31
  • 4
0
votes
0 answers

GitVersion tool fails over develop branch does not exist

We want to integrate GitVersion in our build pipeline for semantic versioning. We are seeing the following error on a repo which doesn't have develop branch: ERROR [06/07/22 16:04:53:53] An unexpected error…
0
votes
0 answers

Semantic Versioning on multiple services in the same Github repository using GH Actions

Our team uses a mono-repo, with several microservices, and some common packages between them. I am tasked with adding CI/CD automation, and traditionally I rely in Git tags for the sem-ver and utilize comments to decide on major/minor/patch. The…
Sam Hammamy
  • 10,819
  • 10
  • 56
  • 94
0
votes
1 answer

Why did npm update axios fail to update but npm uninstall then install can?

I used "axios": "^0.19.2", running npm i gave the warning "npm WARN deprecated axios@0.19.2: Critical security vulnerability fixed in v0.21.1." so I run npm update -S axios to update it. But it failed to update axios. I run yarn upgrade axios but it…
Qiulang
  • 10,295
  • 11
  • 80
  • 129
0
votes
0 answers

Semantic software versioning and application design change

I have a concern, I do not know which position is the one that increases in the version number of an application when you make changes in the design, whether it is a color change, a menu change or the minimum change. If, for example, before having…
0
votes
0 answers

why ^ resolved unexpectedly?

according to the following rule, ^1.2.3 is >=1.2.3 <2.0.0 ^0.2.3 is >=0.2.3 <0.3.0 (0.x.x is special) ^0.0.1 is =0.0.1 (0.0.x is special) ^1.2 is >=1.2.0 <2.0.0 (like ^1.2.0) I am wondering why there is the difference as below…
0
votes
1 answer

How to increment the version of package using semantic-versioning, if several bugfixes and a new backward compatible feature have been added?

The semantic versioning system states that a backwards compatible bugfix means that you increment the patch version number (z in x.y.z). It also states that a backwards compatible feature addition should be introduced by incrementing the minor…
Milind Sharma
  • 152
  • 1
  • 2
  • 10
0
votes
1 answer

semantic-release does not update package.json of my Angular library

I have this Angular library uploaded to a package registry that I created on Gitlab. I've already been able to upload my library successfully to this registry using the CI. I now want to implement semantic versionning to this library, but I'm not…
gabhar
  • 187
  • 1
  • 4
  • 14
0
votes
2 answers

How to validate version to accept 4.4+ but not 4.4+.0

I have wrote regular expression to accept following type of versions "a.." ---> any version of "a" "a.b.*" ---> any version of "a.b" "a.b+" ---> "a.b" or later "a.b.c+" ---> "a.b.c" or later An example: "4.2.2+", "4.3.*,…