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

When to increase minor version with SEMVER?

I have a website I'm developing. I try to use SEMVER with any changes I make. Sometimes I'm not sure when I need to bump up the minor version. For example, I have my website/app at v0.9.0. I have this deployed on a production site. One day, I decide…
Jake Wilson
  • 88,616
  • 93
  • 252
  • 370
0
votes
1 answer

Semantic Versioning (Caret)

I have a question related with the semantic versioning in projects where are in "beta" phase. Imagine that I have a plugin and it's version is 1.1.1-beta.1, some days before, I upgrade my plugin and then, the new version is 1.1.1-beta.2. But... this…
0
votes
1 answer

Express version routing with semver

I'm using express-routes-versioning to version my routes. app.post('/messages', authUser, routesVersioning({ "1.0.5": function(req, res) { moduleMessages.addV105(req, res); } }, function(req, res) { moduleMessages.add(req,…
Chris
  • 4,255
  • 7
  • 42
  • 83
0
votes
1 answer

How to add dependency to NPM package so that I get the latest version that ends with a specific tag

The npm package for NW.js (package name "nw") has versions like this: 0.16.0-beta2sdk, 0.16.0-beta1sdk, 0.15.4, 0.15.4-sdk, 0.15.3, 0.15.3-sdk, 0.15.2, 0.15.2-sdk,... I am currently using nw as a dependency in my package.json manifest, and I was…
peanutman
  • 327
  • 1
  • 2
  • 8
0
votes
0 answers

Rewrite after 1.0.0-beta

Some time ago I've released an open source project with version 1.0.0-beta (it was it's first pre-release). Currently I'm working on a rewrite (so a lot of code changes and documentation won't be up-to-date anymore). What version should I give it…
Bob
  • 873
  • 1
  • 8
  • 21
0
votes
1 answer

Which tool is used by the doctrine ORM project to automatically tag release versions?

i.e. https://github.com/doctrine/dbal/releases v2.2.4 Total issues resolved: 7 etc. etc. PS. I'm not asking about the css style, but the version number, commit number and commit messages Thanks
cassvail
  • 53
  • 4
0
votes
1 answer

What version number is considered as stable from composer?

I would like to know, if e.g. 0.1.0 is already stable concerning a composer install. I am familar with the SemVer Tags and I know, that the API can change with every realease which is not the first major (1.0.0) but still: the tag is a fixed state…
Fuzzyma
  • 7,619
  • 6
  • 28
  • 60
0
votes
1 answer

How to use gitversion on older codebase

I tried running gitVersion on extremely old and complicated codebase that was migrated with git-tfs. I do get results in most branches but they are incorrect. How do I get started with existing repositories? How do I debug the results so I know…
Ben L
  • 1,449
  • 1
  • 16
  • 32
0
votes
0 answers

Is changing the "main" property in bower.json considered a breaking change?

Let's say I maintain a library called foo. Currently, it's at version 1.0.0. Its bower.json looks like this: { "name": "foo", "version": "1.0.0", "main": "dist/foo.js", // ... } I want to move foo.js out of the dist/ folder and to the top…
Evan Hahn
  • 12,147
  • 9
  • 41
  • 59
0
votes
0 answers

Write a file with the version number during Heroku deployment

I want the current code version to be available as a variable at runtime in my express/node.js project running on Heroku. In the development environment I use a git describe node module and have it give me a semver string, but in the production…
tremby
  • 9,541
  • 4
  • 55
  • 74
0
votes
1 answer

npm CLI with semantic versioning that includes > (greater than) symbol

Playing around with npm's semver, most of it seems to translate well to the npm CLI, e.g.: npm install somepackage@~1.0.0-rc ... will include everything greater than the 1.0 version in the same minor range. But to include a greater than symbol,…
brandonscript
  • 68,675
  • 32
  • 163
  • 220
0
votes
1 answer

Semantic versioning : Incrementing by two

Had a question related to Semantic Version We have two levels of customers - Levels 1 & 2. We have a current release (Say 1.0.2). We did a release for Level 1 with a minor number change (1.0.3) - but then decided that it will not go to Level 2. Now…
anoopelias
  • 9,240
  • 7
  • 26
  • 39
0
votes
1 answer

Pre-Release and Build Version Numbers in NuGet

What is considered a pre-release package in NuGet, is it anything that has a dash followed by something e.g. 1.0.0-something? Also, how can you use a build number using NuGet? The NuGet docs about versioning say that you can use 1.0.0-build123.…
0
votes
2 answers

RegEx substitution works in Ruby gsub, but not with sed

I'm trying to strip prefixes from a SemVer, i.e, making 1.2.3-prefix.42 into 1.2.3. I'm using this RegEx found in…
mokagio
  • 16,391
  • 3
  • 51
  • 58
0
votes
2 answers

Npm install does not work

I have a problem with my npm. This is my error: I try to uninstall nodejs and install it but my error stays, then I try the command npm install npm, Have the same error and npm -v does not work too.