Handling versions below 1.0.0

Hi 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

[bcoe]

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.

[eisenreich]

I started with a new repository and I would also like to start with version 0.1.0 - the version number is the version.txt, configured with bumpFiles.

If you like to release the first version with 0.1.0, just use the following:

npx standard-version --release-as 0.1.0

this should release the first version with 0.1.0 and then you can just use

npx standard-version

which should bump the version according the SemVer logic - also < 1.0.0 versions.