Pre-release and Build Metadata
What you'll learn: How to use version suffixes and build identifiers to communicate release maturity and testing status to users and systems.
The Need for Release Qualifiers
Once you understand Semantic Versioning (like 1.4.2), you need a way to mark versions that aren't quite "production-ready" or to track which specific build produced an artifact. Pre-release identifiers and build metadata solve this problem.
Pre-release Identifiers
Think of pre-release versions like movie screenings before the official premiere. They're the same content, but marked for limited audiences.
Common suffixes include:
alpha— Very early, unstable testing (1.4.2-alpha.1)beta— Feature-complete but may have bugs (1.4.2-beta.3)rc(release candidate) — Final testing before release (1.4.2-rc.2)
The hyphen and dot structure matters: 1.4.2-beta.3 means "the third beta build of version 1.4.2." These versions sort before the final 1.4.2 in SemVer order, so package managers know they're pre-release.
Build Metadata
Build metadata identifies which specific build produced an artifact, useful for tracing issues back to a commit or build server run. It's appended with a plus sign: 1.4.2+build.2543 or 1.4.2-rc.1+20240315.abc123.
Unlike pre-release identifiers, build metadata doesn't affect version precedence. Both 1.4.2+build.100 and 1.4.2+build.200 are considered equal versions; the metadata is for human tracking only.
Combining Both
You can use both together: 1.4.2-beta.3+build.1829.git.abc123 tells you it's the third beta AND which commit/build produced it.
Key Takeaway: Pre-release suffixes (-alpha, -beta, -rc) signal maturity and affect version ordering, while build metadata (+build.xyz) provides traceability without changing version precedence.