Dev workflow and DevOps · Concept

Semantic versioning

A rule for version numbers such as 2.4.1, where each part tells you how risky an upgrade is: breaking change, new feature or bug fix.

Packages · updated

How it works

A version has three parts, MAJOR.MINOR.PATCH. A patch release (2.4.1 to 2.4.2) only fixes bugs, a minor release (2.4 to 2.5) adds features without breaking anything, and a major release (2 to 3) may break existing code. Versions below 1.0.0 make no promises at all, and tags such as 3.0.0-beta.1 mark pre-releases.

Package managers build on it. In package.json, ^2.4.1 accepts any 2.x release from 2.4.1 up, and ~2.4.1 accepts only 2.4.x patches. The scheme only works if maintainers follow it, and not all do, which is one more reason to commit a lockfile and read the changelog before a major upgrade.

More in Dev workflow and DevOps

Packages

All 21 Dev workflow and DevOps terms

Crafted in the dark. Shipped to the world.

Tell us what you are building. You get a private project space with a proposal and a line-by-line quote within a day.