TOPIC DEVOPS
Semantic Versioning what 2.1.3 promises
IN 10 SECONDS
A standard formatting rule for code releases: MAJOR.MINOR.PATCH. Increment MAJOR for breaking changes, MINOR for features, and PATCH for backward-compatible bug fixes.
GOTCHA Releasing breaking changes in minor/patch updates violates SemVer promises, causing consumer pipelines to break during automatic dependency updates.
HOW VERSION RESOLUTION FLOWS
01 Bug Fix developer patches a security bug, incrementing PATCH: v1.0.1.
02 New Feature adds a new endpoint (backward compatible), incrementing MINOR: v1.1.0.
03 Breaking Change wipes out legacy API support, incrementing MAJOR: v2.0.0.
04 Client resolve clients download updates safely using version ranges (~ or ^) matching their requirements.
POKE IT YOURSELF
npm semver v2.1.3 — check if a version fits within range constraints
git tag -a v2.0.0 -m "breaking release" — publish a SemVer tag to git repository history
Drill this topic →
~65 sec read