SemVer Validator
Validate semantic version strings and parse major, minor, patch, pre-release, and build metadata.
Related Tools
@Email Address Validator
Validate email addresses against RFC 5322 rules with local part, domain, and TLD breakdown.
📞Phone Number Formatter
Format phone numbers in E.164, national, and international formats for 10 countries.
🔗Domain Name Validator
Validate domain names against RFC 1035 rules: length, characters, labels, and TLD.
FAQ
- What is Semantic Versioning (SemVer)?
- SemVer is a versioning scheme defined at semver.org. A version is formatted as MAJOR.MINOR.PATCH, where MAJOR changes for incompatible API changes, MINOR for new backward-compatible features, and PATCH for backward-compatible bug fixes. Optional pre-release and build metadata can follow.
- What is the format for pre-release versions?
- Pre-release versions are denoted by a hyphen after the patch number followed by dot-separated identifiers: 1.0.0-alpha, 1.0.0-alpha.1, 1.0.0-0.3.7. Identifiers must be alphanumeric or hyphens. Numeric identifiers must not have leading zeros.
- How are two SemVer versions compared?
- SemVer precedence: compare MAJOR, then MINOR, then PATCH numerically. Pre-release versions have lower precedence than the release (1.0.0-alpha < 1.0.0). Build metadata is ignored for precedence. Within pre-release, numeric identifiers compare numerically and alphanumeric compare lexicographically.
Enter a semantic version string (e.g. 1.2.3-alpha.1+build.42) to validate against the SemVer 2.0.0 specification. Parses and displays major, minor, patch, pre-release identifier, and build metadata. Also supports comparing two version strings to determine which is newer. Follows semver.org specification precisely.