Geek Answers Handbook

Indermediate sub-patch Node.js package version

I provide a companion package that matches the version of the main NPM package, already in major.minor.patch format (for example, 1.3.1 ).

I don’t want to break version correspondence between the main and accompanying package. Is it possible to free intermediate subpackages for an accompanying package that match

 >=1.3.1 <1.3.2

semver restriction? Similarly 1.3.1.1 .

Even if the constraint cannot be matched, what is the convention for the patch for 1.3.1 to make it non-overlapping 1.3.2 ?

+7
npm semantic-versioning
source share
1 answer

Like http://semver.org/ state

Given the version number of MAJOR.MINOR.PATCH, increase the value:

  • BASIC version, when you make incompatible API changes,
  • MINOR version when you add functionality in a backward compatible manner and
  • PATCH when you do backward compatibility bug fixes.
  • Additional labels for pre-release and build metadata are available as extensions to the MAJOR.MINOR.PATCH format.

Since there are no sub-patches in SemVer, you can mark your version with a tag, for example 1.3.2-alpha1 or similar.

npm does not install tagged versions; it usually releases candidates labeled rc , alphas, betas, etc., without explicitly indicating that you want to install such a version.

+4
source share

More articles:


All Articles