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
2 answers

How do I prevent NuGet from upgrading a package after switching to semantic versioning from date-based versioning?

We've recently started using our own internal NuGet server to house packages that are common to many of our internal projects. Originally, every project we work on is versioned with the build date in the…
Sumo
  • 4,066
  • 23
  • 40
-1
votes
1 answer

When I create a new project by using npm create vite@latest and do npm install, I get the following error

semver <7.5.2 Severity: moderate semver vulnerable to Regular Expression Denial of Service - https://github.com/advisories/GHSA-c2qf-rxjj-qqgw fix available via npm audit fix --force Will install eslint-plugin-react@7.25.3, which is a breaking…
-1
votes
1 answer

How to avoid version number conflict between master and bugfix branch when using semantic versioning

A master branch in git following semantic versioning has released below versions in its lifecycle till date. 1.0.0 -> 1.0.1 -> 1.1.0 -> 1.2.0 A hotfix branch is cutoff named hotfix\1.0.0 for a bug fix/compatible extension, which will necessitate a…
Nitesh
  • 31
  • 4
-1
votes
1 answer

What does two version requirements on single line mean in a package-lock.json?

I was looking through my package-lock.json and I came across this requirement: "requires": { "bootstrap": ">=4.5.3 <5.0.0", } What does it mean to have two version expressions in one line like this? I'm writing something to compare package…
-1
votes
1 answer

parsing a masive csv file having a problem with bad version number of the software how do i format quickly 5 million rows

Here's a sample of my data: from io import StringIO data = StringIO("""software,version Visual C++ Minimum Runtime,11.0.61030 Visual C++ Minimum Runtime,11.0.61030 Visual C++ Minimum Runtime,11.0.61030.0.0.0.0""") Notice that the last record the…
-1
votes
1 answer

Using semver, should pre-release versions be based off the previous version number, or the next version number?

Doing a pseudo-CD strategy for dev environments and we want to make sure all interim builds are tagged and versioned in a way that provides traceability but also conforms to semver so that helm etc doesn't yell at us and also I can sleep at night…
ChickenWing
  • 639
  • 9
  • 24
-1
votes
1 answer

how increment works for a variable in Azure pipeline

let say i have defined few variables in my yaml: major: 0 minor: 0 patch: $[counter(variables['minor'], 0)] #this will reset when we bump minor myVersion: '$(major).$(minor).$(patch)-$(Build.BuildId)' I have few doubts about it's working. I know…
-1
votes
1 answer

Updating dependency version that doesn't change anything in your package

Say you have a package Foo that relies on package Bar. Initially Foo v1.0.0 relied on Bar v1.0.0. Bar updated to v2.0.0. You now update the dependencies of Foo so it now requires Bar v2.0.0. Since this upgrade of Bar does not break, add, or fix any…
IMB
  • 15,163
  • 19
  • 82
  • 140
-1
votes
1 answer

Command to check if there is any range versions in the dependencies section of the package.json

Basically I want CI to fail if the dependencies section of the package.json contains any range operator. devDependencies could contain anything thought. Some CLI command would be perfect. Any suggestions?
IAfanasov
  • 4,775
  • 3
  • 27
  • 42
-1
votes
1 answer

Semantic Versioning for command line tools

The SemVer specs state that you should increase the MAJOR version when you make incompatible API changes, MINOR version when you add functionality in a backwards-compatible manner, and PATCH version when you make backwards-compatible bug…
pixelistik
  • 7,541
  • 3
  • 32
  • 42
-1
votes
1 answer

Semver library is giving me an invalid version for 0.0.001

I have this piece of code: const semver = require('semver'); let oldestVersion = '0.0.001'; let youngestVersion = '9999.99.999'; let youngestPackageName = null; let oldestPackageName = null; Object.keys(confirmProjects).forEach(k => { …
user7898461
-1
votes
1 answer

Use semver package to convert ^4.2.3 to 4.2.3

Using the semver NPM package https://docs.npmjs.com/misc/semver is there a way to convert a package version like so ^4.2.3, to one that is without the ^? I just need to do string manipulation to remove any preceding characters that are not numbers,…
Alexander Mills
  • 90,741
  • 139
  • 482
  • 817
-1
votes
1 answer

SemVer major upgrade or not?

I have an artifact that is not used directly. These artifacts contain the server that runs users application. The API that is visible to users (i.e. to 3rd parties) is well defined in a separate library. Now, I am doing some changes in the server.…
igr
  • 10,199
  • 13
  • 65
  • 111
-1
votes
1 answer

How to install version from nexus with minor version

I have many version of my appliction in nexus with versions 1.52.0-xxxxx the xxxx is different dates I have also version of 1.53 and 1.54 How I can get the latest 1.52.0-with the latest date without get the 1.53 version and later this is my…
user1365697
  • 5,819
  • 15
  • 60
  • 96
-2
votes
1 answer

Semantic version sort with SQL

How to sort semantic versions properly according to its rules in https://semver.org/ in SQL directly? Examples: 1.0.0-alpha, 1.0.0-alpha.1, 1.0.0-0.3.7, 1.0.0-x.7.z.92, 1.0.0-x-y-z.
kotsky
  • 17
  • 3
1 2 3
44
45