Version Scheme - Semantic versioning (Semver)

Card Puncher Data Processing


Semantic Versioning 2.0.0

Version format of X.Y.Z (Major.Minor.Patch).

Semantic versioning requires that versions with breaking changes must increment the major version number. For example, a library that removes a public function after its 3.5.8 release must bump its version to 4.0.0 in its next release.


For example, if your library has:

  • a major release version of 1,
  • a minor release version of 2
  • and point release version of 3

the version would be 1.2.3.

Release Status

Semantic versions can also have alphanumeric qualifiers which are often used to denote release status.

An example of such a qualifier would be a version like “1.2.3-BETA” where BETA signals a stage of testing meaningful to consumers of a software component.

Discover More
Card Puncher Data Processing
Code Versioning - Versioning scheme

The different scheme on the version number of a release of a module. it's just a numberNick_Craver/status/910109822326099969?s=03Nick Craver APISemantic...
Javascript Package - Package.json

Package.json is used by npm to store metadata for projects published as package. The package.json files: * serves as documentation for what packages your project depends on. * allows you to specify...
Npm Nexus Publish
Heading Text Not found

in Javascript A registry is: A repository for packages that implements the CommonJS Compliant Package Registry specification for reading package info...
Javascript Package - Version

version in a Javascript package can be found in the package.json file as property. See also - semver Tags...
Card Puncher Data Processing
Maven - Version

Version in Maven can refere to: the version of maven the version of an artifact. To get the Maven Version, just execute this option Version is one component of the artifact defined in the...

Share this page:
Follow us:
Task Runner