Non-SemVer package versions (with 4 parts) #7376
Labels
Area:PackageDefinition
Resolution:Question
This issues appears to be a question, not a product defect
WaitingForCustomer
Applied when a NuGet triage person needs more info from the OP
First of all, I hope this is the right place to ask such a question. If not, please feel free to close this and direct me in the right direction.
Is using a SemVer compatible version number a requirement for NuGet packages? The only documentation I could find on this topic talks about SemVer for package versions but it also briefly mentions the possibility of having four part versions:
So, is it possible to use a version number that consists of four parts for a NuGet package? And if it is possible: Does that come with any disadvantages?
The use case is that we are currently working on a database driver and wondered whether we could include the version number of the database in the version of the library to communicate to users which version of the library is compatible with which version of the database. Since the database already has a version number that consists of three parts (like
0.3.0
), a fourth part seems to be necessary to differentiate between versions of the library for the same database version (like0.3.0.1
,0.3.0.2
, and so on).(Some context: The database in question is JanusGraph and we are currently discussing about how to handle versioning for driver libraries.)
The text was updated successfully, but these errors were encountered: