Prerelease versions in nightly feed should use semver 2.0
See original GitHub issueThe current version scheme is causing an issue with Dependabot:
Bump coverlet.collector from 1.3.1-preview.24.g6479f627e4 to 1.3.1-preview.8.ge848786b0d
Prerelease versions in nightly feed should use semver 2.0 (NuGet support). See coverlet package history. Specifically, the git sha should be added as metadata; e.g. 1.3.1-preview.24.g6479f627e4
should be 1.3.1-preview.24+g6479f627e4
so it’s ignored in version precedence.
That said, there is another Dependabot issue that will be relevant but don’t let that stop you using proper semver 2.0 versions.
Issue Analytics
- State:
- Created 3 years ago
- Comments:12 (3 by maintainers)
Top Results From Across the Web
SemVer, NuGet, and Nightly Builds | You've Been Haacked
When you're ready to release, you just remove the pre-release part and that version is considered “higher” than all the pre-release versions.
Read more >Semantic Versioning 2.0.0 | Semantic Versioning
Patch and minor versions MUST be reset to 0 when major version is incremented. A pre-release version MAY be denoted by appending a...
Read more >Using semver, should pre-release versions be based off ...
Doing a pseudo-CD strategy for dev environments and we want to make sure all interim builds are tagged and versioned in a way...
Read more >Supporting Semantic Versioning 2.0.0 - The NuGet Blog
Adopting SemVer provided NuGet support of pre-release package versions. ... and exposed on the feeds, they will be able to parse the version...
Read more >What is the significance of reaching major version 1.0.0?
Patch and minor versions MUST be reset to 0 when major version is incremented. Semantic Versioning 2.0.0. So yes there is a magical...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@MarcoRossignoli yes, I linked to the Dependabot issues above, but for some reason thought switching to using metadata for the git sha would help as it would be stripped. However, a quick look at the relevant Dependabot source confirms that the prerelease part of the version is still compared lexically, without considering dot separated identifiers consisting of only digits that should be compared numerically:
😞
@AArnott yes, the first issue I referred to was semver 2.0 versions not handled correctly for nuget pre-release dependencies.