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

Semantic Versioning for Visual Studio Solution

My team has a fairly large set of desktop applications with many shared libraries between them all in one common solution file in our repository. We'd like to use semantic versioning for a number of reasons, chief of which is to make it easier for…
Chris Bush
  • 229
  • 1
  • 13
0
votes
1 answer

Pip Install Semantic Version with Metadata not upgrading

I have two versions of my python build: 16.1206.43542 17.0817.221945+f4cc396 The only really difference I can see is the ending metadata. When I run pip install package, the version 16.1206.43542 is installed and not the latest. Is this the proper…
supreme Pooba
  • 868
  • 1
  • 7
  • 14
0
votes
1 answer

Warning on default Laravel Spark version constraint without upper bound

I recently created a fresh Laravel Spark project following the official documentation. This set the version constraint for laravel/spark to *@dev. Now, PhpStorm warns: The version constraint has no upper bound – this is not a good idea. See…
0
votes
1 answer

semantic versioning, bug-fix-releases of previous versions and precedence in tree structure

We use semantic versioning. Suppose we have some software release with a version number of e.g. 2.1.1. Because of an API change the next release has version number 3.0.0. Now let us suppose that a bug is found which occurs both in version 2.1.1 and…
coproc
  • 6,027
  • 2
  • 20
  • 31
0
votes
0 answers

Inconsistent behavior npm

I'm using npm install with advanced range, e.g. npm i karma@^1.0.0 and for Linux and OSX I get the latest version of package, but for windows platform, npm ignores range (caret symbol) and installs v.1.0.0 According to npm docs, I have to enclose…
Bob
  • 773
  • 1
  • 10
  • 20
0
votes
1 answer

npm installs wrong package version

I'm trying to install karma using the following command npm i karma@^1.0.0. npm installs karma@1.0.0 rather than latest version karma@1.6.0. After a little investigation, I figured out that these commands work: npm i karma@^1 and npm i…
Bob
  • 773
  • 1
  • 10
  • 20
0
votes
1 answer

sbt, how to maintain own libraries?

Let's assume we have three projects (version in brackets): A (0.0.1) B (0.0.1), depends on A (0.0.1) C (0.0.1), depends on B (0.0.1) C depends on A & B. Now we want to use this libraries as dependencies in our new project (D). So we add deps: C…
Alexander Kondaurov
  • 3,677
  • 5
  • 42
  • 64
0
votes
1 answer

npm ERR! peer dep missing: zone.js@^0.7.2 - but zone.js 0.8.4 installed

When I get the list of my packages by npm ls command I see this alert: npm ERR! peer dep missing: zone.js@^0.7.2, required by @angular/core@2.4.10 Here is My package.json dependencies: "dependencies": { "@angular/common": "2.4.x", …
Artem
  • 487
  • 1
  • 8
  • 19
0
votes
1 answer

NPM: How to get bumped version in my CLI command?

Let's say i have a library and when i compile it with webpack i also add a banner such as this one: // LibraryName vX.X where vX.X is its version. I want to compile it with npm preversion script. As here: "preversion": "gulp build --version…
0
votes
2 answers

Should I keep testing code or implement more functionality?

I have a side project that I love to code, I spend time with it when I can, since I'm still finishing my university studies. When I started it, I barely knew good programming practices and TDD among other things, I only coded it for fun. Several…
transgressoft
  • 155
  • 2
  • 13
0
votes
1 answer

Semver package.json version acceptable numbers

I just have a quick question since I can't find a correct versioning formats. For node.js modules package manager package.json 0.0.0 -> acceptable 10.0.0 -> acceptable 0.10.0 -> acceptable 0.0.10 -> acceptable? 0.0.01 -> not acceptable? does…
0
votes
1 answer

How to semantically version a change to a CSS color property

I maintain a CSS framework and am trying to follow semantic versioning in a way that makes the most sense. Would changing the value of non critical property (like the color of an element) be considered a minor change or a patch change? If I am at…
Mike Hamilton
  • 1,519
  • 16
  • 24
0
votes
1 answer

semver caret behavior differ between npm install and update

This is my package.json: { "name": "pr", "version": "1.0.0", "description": "", "main": "index.js", "scripts": { "test": "echo \"Error: no test specified\" && exit 1" }, "author": "", "license": "ISC", "devDependencies": { …
ShlomiTC
  • 446
  • 4
  • 12
0
votes
1 answer

When are web components compatible according to the semver specification?

Theoretically speaking I'm trying to figure out when a web component linter reading package.json for JSPM web component dependencies can determine whether a web component dependency graph can be constructed without having any duplicate web…
Ole
  • 41,793
  • 59
  • 191
  • 359
0
votes
2 answers

How do I get TFS 2015 to parse 3 digit versioning for NuGet packaging

When I set my TFS 2015 build definition, that is creating a NuGet package, I set the Build Number format with: $(BuildDefinitionName)_$(Major).$(Minor)$(rev:.r) Where Major and Minor or just variables that I defined. When I use the step "NuGet…
Antebios
  • 1,681
  • 1
  • 13
  • 22