-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for semver suffixes (prerelease + build metadata) #37
Milestone
Comments
Note that this needs a rework of the logic on how the "latest package" is determined. I'll go the route of nuget and only using "stable" package versions (without suffix) for that, only serving packages with a suffix on explicit requests. |
kMutagene
changed the title
Add support for prerelease semver suffix
Add support for semver suffixes (prerelease + build metadata)
Jun 21, 2024
kMutagene
added a commit
that referenced
this issue
Jun 21, 2024
- SemVer has fields for PreRelease and BuildMetadata suffixes - SemVer has parsing/writing functions - add respective flat fields to ValidationPackageMetadata - add respective static methods to ValidationPackageMetadata and ValidationPackageIndex - added tests
kMutagene
added a commit
that referenced
this issue
Jun 21, 2024
kMutagene
added a commit
that referenced
this issue
Jun 21, 2024
kMutagene
added a commit
that referenced
this issue
Jun 21, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
see https://semver.org/#spec-item-9
Needed for adding distinctions especially for specification validation, where the package version should be equal to the specification version, but the specs themselves often have prerelease suffixes (e.g. 2.0.0-draft)
The text was updated successfully, but these errors were encountered: