DevOps Beginner
Semantic Versioning¶
SemVerVersioningRelease 3 min read
MAJOR.MINOR.PATCH verzovani software.
Pravidla¶
MAJOR.MINOR.PATCH (napr. 2.4.1)
MAJOR - breaking changes
MINOR - nove funkce, zpetne kompatibilni
PATCH - bugfixy
Pre-release: 3.0.0-alpha.1, 3.0.0-rc.1
Practical Examples and Automation¶
Proper versioning is crucial for reliable dependency management. When you increase the MAJOR version (e.g., from 2.x to 3.0.0), you signal breaking changes — users of your library must modify their code. A MINOR version (2.4.0 to 2.5.0) adds new features but existing code works without changes. A PATCH (2.4.0 to 2.4.1) fixes bugs.
By combining Conventional Commits with semantic-release, you achieve full automation: a feat: commit bumps MINOR, fix: bumps PATCH, and BREAKING CHANGE: bumps MAJOR. Pre-release versions (alpha, beta, rc) allow testing before official release. Lockfiles (package-lock.json, Pipfile.lock) ensure reproducible builds by pinning exact versions of all dependencies, while ranges (^2.4.0, ~2.4.0) in package.json define compatible version ranges.
Shrnuti¶
feat: = MINOR. fix: = PATCH. BREAKING CHANGE: = MAJOR. Automatizujte.
Need Help with Implementation?¶
Our team has experience designing and implementing modern architectures. We’re happy to help.