fix: range exact/non-equal matches ignore build metadata
Build metadata does not affect precedence (SemVer 2.0.0 §10), so the Eq and Neq constraints now use SemanticVersionComparer.Priority instead of the structural == operator. This makes [1.2.3] match 1.2.3+build, consistent with precedence semantics. Add a failing-then-passing test.
This commit is contained in:
parent
b4ca01580a
commit
2ea7866e3b
3 changed files with 14 additions and 2 deletions
|
|
@ -19,6 +19,7 @@ This project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.htm
|
|||
### Fixed
|
||||
|
||||
- Reject invalid SemVer identifiers when parsing versions.
|
||||
- Range exact and non-equal comparators ignore build metadata when matching versions.
|
||||
|
||||
### Removed
|
||||
|
||||
|
|
|
|||
Loading…
Reference in a new issue