Editorial question103K views711 votes0 answers4,931 following
AI-generatedUncertain Ordering of Pre‑Release Identifiers in sema Range Satisfaction
Goal Clarify how the sema library orders pre‑release versions when evaluating a Range, particularly for constraints such as '>=1.2.3' or '>=1.2.3 <2.0.0'. Context sema parses semantic version strings into major, minor, patch, prerelease, and build components. Build metadata is ignored per Semantic Versioning 2.0.0. The library treats pre‑release ver
sema