Handling versions below 1.0.0
See original GitHub issueHi There, Please do you support a different handling model for version under 1.0.0?
NPM for example treats **^**0.1.0 as **~**0.1.0 for all versions bellow 1.0.0
https://docs.npmjs.com/misc/semver
~1.2.3 := >=1.2.3 <1.(2+1).0 := >=1.2.3 <1.3.0
~1.2 := >=1.2.0 <1.(2+1).0 := >=1.2.0 <1.3.0 (Same as 1.2.x)
~1 := >=1.0.0 <(1+1).0.0 := >=1.0.0 <2.0.0 (Same as 1.x)
~0.2.3 := >=0.2.3 <0.(2+1).0 := >=0.2.3 <0.3.0
^1.2.3 := >=1.2.3 <2.0.0
^0.2.3 := >=0.2.3 <0.3.0
^0.0.3 := >=0.0.3 <0.0.4
So upgrade a minor number only if there is a breaking change. Otherwise patch number is increased.
Thanks a lot!
Best regards, Andrej
Issue Analytics
- State:
- Created 7 years ago
- Comments:9 (6 by maintainers)
Top Results From Across the Web
Semantic Versioning 1.0.0
A pre-release version number MAY be denoted by appending an arbitrary string immediately following the patch version and a dash. The string MUST...
Read more >What to use as an initial version? [closed] - Stack Overflow
Version 1.0.0 defines the public API. The way in which the version number is incremented after this release is dependent on this public...
Read more >Versions and Build Numbers - Concourse Tutorial
If you don't care about the semantic meaning of your semver resource type, then start at 0.0.1 and bump the PATCH version only....
Read more >Semantic Versioning - CommandBox : CLI, Package Manager ...
CommandBox> package version 1.0.0 ... like you would expect to request all versions above, below, or between other versions. ... Any version less...
Read more >SemVer - Use semantic version numbers - manpages.ubuntu!
0 < 1.11.0". 2. A pre-release version number MAY be denoted by appending an arbitrary string immediately following the patch version and a...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I know not 100% of folks agree, but I’m definitely of the school of thought that, versions are cheap, just make your first library version
v1.0.0
. Maybe we could write this into the README as part of our opinionated guidelines.I understand the other arguments, folks don’t want to announce their library as stable when it’s in an extreme amount of flux, but I think it’s not worth the edge-cases it creates around semver. Better that while your library is in flux, IMO, you bump a few majors.
I started with a new repository and I would also like to start with version
0.1.0
- the version number is theversion.txt
, configured withbumpFiles
.If you like to release the first version with
0.1.0
, just use the following:this should release the first version with 0.1.0 and then you can just use
which should bump the version according the SemVer logic - also < 1.0.0 versions.