Jeff Walker
Jeff Walker
Currently, the `Parse` and `TryParse` methods do not validate the `maxLength` argument. So if it is negative, they report that as an error with the version string being too long...
Add a class that represents a SemVer version range and can check whether a version is within the range. This functionality would serve as the core of implementations needing to...
A lot of methods have been marked `[Obselete]` as part of the fixes for v2.1.0 and v2.2.0. As part of v3.0.0, those `[Obsolete]` methods need to be removed.
The primary constructor allows the construction of a `SemVersion` instance with negative values for Major, Minor, and Patch.
As of Semver v2.1.0, it will ship with DLLs targeting .NET 4.5.2, .NET Standard 1.1, and .NET Standard 2.0. However, this includes support for versions with are no longer supported...
Currently, Appveyor assigns a version number based either on the tag being built, or the version number in `appveyor.yml` along with a build number to make it unique. Instead, find...
By looking at https://www.nuget.org/stats/packages/semver?groupby=Version it appears there are lots of people still using the 1.x version. It might help them transition if there were release notes for what changed in...
See https://github.com/maxhauser/semver/community
Per the discussion in PR #25, the implicit conversion to string should be removed. First, it shouldn't be an implicit conversion because it can fail. But even if it were...
The js macro will accept an expression like `+ +x` as an increment of `x`