DevOps Beginner

What is Semantic Versioning?

A versioning scheme using MAJOR.MINOR.PATCH numbers that communicates the nature of changes in each release.

Semantic Versioning (SemVer) uses three numbers: MAJOR (breaking changes), MINOR (new features, backward compatible), PATCH (bug fixes, backward compatible). Example: 2.4.1 → 2.5.0 (new feature) → 3.0.0 (breaking change).

Pre-release versions use suffixes: 1.0.0-alpha, 1.0.0-beta.1, 1.0.0-rc.1. SemVer enables dependency management tools to automatically determine compatible updates. Most package managers (npm, pip, cargo) rely on SemVer.

Learn More About This Topic

n8n CLI for Beginners

Related reading

Webhook Automation in Practice

Related reading

Microservices with Docker and Kubernetes

Related reading

Related Terms

Log Aggregation

The process of collecting, centralizing, and indexing log data from multiple sources for unified search and analysis.

A technique that allows enabling or disabling features in production without deploying new code, enabling safe rollouts and A/B testing.

A practice where Git repositories serve as the single source of truth for both application code and infrastructure configuration.

A platform for continuous code quality inspection that detects bugs, vulnerabilities, and code smells through static analysis.

Kubernetes ConfigMap

A Kubernetes object that stores non-sensitive configuration data as key-value pairs, injected into pods as environment variables or files.

Infrastructure Drift

The divergence between the actual state of infrastructure and its defined desired state, caused by manual changes or untracked modifications.

View All DevOps Terms →