semver/CHANGELOG.md

# Changelog

All notable changes to this project will be documented in this file.

This project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).

## [1.0.0] - 2026-05-21

### Added

- This is the initial release of the library.

## [Unreleased]

### Added

### Changed

### Fixed

- Reject invalid SemVer identifiers when parsing versions.
- Range exact and non-equal comparators ignore build metadata when matching versions.
- Avoid infinite recursion when formatting ranges in the short npm (`ns`) form.

### Removed

[1.0.0]: https://code.geekeey.de/geekeey/semver/releases/tag/1.0.0
[Unreleased]: https://code.geekeey.de/geekeey/semver/compare/1.0.0...HEAD
feat: add initial project setup 2026-04-05 08:23:42 +02:00			`# Changelog`

			`All notable changes to this project will be documented in this file.`

			`This project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).`

			`## [1.0.0] - 2026-05-21`

			`### Added`

			`- This is the initial release of the library.`

			`## [Unreleased]`

			`### Added`

			`### Changed`

fix: reject invalid SemVer identifiers when parsing Per SemVer 2.0.0 the core version numbers and numeric prerelease identifiers must not include leading zeroes, and prerelease/build-metadata identifiers must be composed only of ASCII alphanumerics and hyphens. Add IsValidIdentifiers using a vectorized SearchValues lookup for the allowed character set and ulong.TryParse to detect numeric identifiers for the leading-zero check. Add failing-then-passing tests for both invalid and still-valid inputs. 2026-07-11 21:56:56 +02:00			`### Fixed`

			`- Reject invalid SemVer identifiers when parsing versions.`
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. 2026-07-11 21:57:12 +02:00			`- Range exact and non-equal comparators ignore build metadata when matching versions.`
fix: avoid infinite recursion when formatting ranges as short npm TryFormat for the "ns" format returned false for any set that can not be expressed as a caret/tilde range. The public ToString routes through DefaultInterpolatedStringHandler, whose buffer-full fallback re-enters ToString, causing an infinite loop / stack overflow. For "ns", fall back to the full comparator ("n") form when the compact form cannot represent the set, so the call always succeeds for a representable range. A genuine buffer overflow still returns false as before. Add failing-then-passing tests. 2026-07-11 21:57:23 +02:00			- Avoid infinite recursion when formatting ranges in the short npm (`ns`) form.
fix: reject invalid SemVer identifiers when parsing Per SemVer 2.0.0 the core version numbers and numeric prerelease identifiers must not include leading zeroes, and prerelease/build-metadata identifiers must be composed only of ASCII alphanumerics and hyphens. Add IsValidIdentifiers using a vectorized SearchValues lookup for the allowed character set and ulong.TryParse to detect numeric identifiers for the leading-zero check. Add failing-then-passing tests for both invalid and still-valid inputs. 2026-07-11 21:56:56 +02:00
feat: add initial project setup 2026-04-05 08:23:42 +02:00			`### Removed`

			`[1.0.0]: https://code.geekeey.de/geekeey/semver/releases/tag/1.0.0`
			`[Unreleased]: https://code.geekeey.de/geekeey/semver/compare/1.0.0...HEAD`