NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
NuGet · #2427 most downloaded on NuGet
This library implements the Semantic Versioning 2.0.0 specification and the version range specification used by npm.
Last release 2 years ago
no release in 18 months
Release timing varies
gaps range from 2 weeks to 1.6 years
Rarely documented
notes for 6 of 29 stable releases
Nothing withdrawn
no release was ever pulled
12 years old
31 releases · first in 2015
This is a new major version release and introduces breaking changes in behaviour.
This is a new major version release and introduces breaking changes in behaviour.
v, for example v1.2.3, are now considered invalid, and only allowed in loose mode, in accordance with the semantic versioning specification (#58)x or * when includePrerelease is true. For example the range 3.2.x is now satisfied by 3.2.0-beta.1 when previously it was not (#55)includePrerelease is true and the major version is zero. For example, previously the range ^0.2.3 was satisfied by 0.2.3-alpha when includePrerelease is true but now it is not. The behaviour when the major version is non-zero has not changed, for example ^1.2.3 is not satisfied by 1.2.3-alpha (#56)Full Changelog: 2.0.2...3.0.0
One column per quarter.
Add README to Nuget package by @adamreeve in #59
Full Changelog: 3.0.0-beta1...3.0.0-beta2
This is a beta version of the 3.0.0 version, which is a major version change due to introducing some breaking changes.
This is a beta version of the 3.0.0 version, which is a major version change due to introducing some breaking changes.
v, for example v1.2.3, are now considered invalid, and only allowed in loose mode, in accordance with the semantic versioning specification.x or * when includePrerelease is true. For example the range 3.2.x is now satisfied by 3.2.0-beta.1 when previously it was not.includePrerelease is true and the major version is zero. For example, previously the range ^0.2.3 was satisfied by 0.2.3-alpha when includePrerelease is true but now it is not. The behaviour when the major version is non-zero has not changed, for example ^1.2.3 is not satisfied by 1.2.3-alpha.Full Changelog: 2.0.2...3.0.0-beta1
CI update to allow publishing change from 2.0.1 to NuGet (Fixes incorrect range intersection calculation when different ranges use the same version nu
CI update to allow publishing change from 2.0.1 to NuGet (Fixes incorrect range intersection calculation when different ranges use the same version numbers with different operators)
Rename assembly and namespace to SemanticVersioning to match nuget package
Add Parse and TryParse static methods on Version and Range
Add Parse and TryParse static methods on Version and Range
Implement IComparable for Version
Implement IComparable for Version
Fix for range intersection behaviour
Fix for range intersection behaviour
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Your coding agent can read these notes before it upgrades. Set up the MCP server →