Semantic Version with 'v' Prefix Regex for Go

What this pattern does

This page provides a comprehensive, battle-tested regular expression for matching semantic version with 'v' prefix, ported and verified for Go. A rigorously tested regex reduces debugging time and protects your application from edge-case failures. The snippet below is ready to drop into your Go project — whether you're validating in a Gin handler, a gRPC service, or a command-line tool.

Go Implementation

// Semantic Version with 'v' Prefix
// ReDoS-safe | RegexVault — Dev & Systems > SemVer

package validation

import "regexp"

var semanticVersionWithVPrefixRe = regexp.MustCompile(`^[vV]?(0|[1-9][0-9]*)\.(0|[1-9][0-9]*)\.(0|[1-9][0-9]*)(?:-((?:0|[1-9][0-9]*|[0-9]*[a-zA-Z\-][a-zA-Z0-9\-]*)(?:\.(?:0|[1-9][0-9]*|[0-9]*[a-zA-Z\-][a-zA-Z0-9\-]*))*))?(?:\+([a-zA-Z0-9\-]+(?:\.[a-zA-Z0-9\-]+)*))?$`)

func ValidateSemanticVersionWithVPrefix(s string) bool {
    return semanticVersionWithVPrefixRe.MatchString(s)
}

// Example
// fmt.Println(ValidateSemanticVersionWithVPrefix("v1.0.0")) // true

Test Cases

When to use this pattern

This pattern is drawn from the Dev & Systems > SemVer category and carries a ReDoS-safe certification. That matters for Go developers because Go's RE2 engine is inherently safe from catastrophic backtracking, but this pattern has been additionally verified for correctness. RegexVault audits patterns against known backtracking attack vectors, ensuring you have the necessary context before using this regex in a high-stakes production environment.

Common Pitfalls

Technical Notes

The v prefix is a convention in Git tagging but not part of SemVer 2.0.0 spec. Strip the v before semantic comparison. Go modules use v+SemVer as their module versioning scheme.