Semantic Versioning of Packages

[Steven Dusing]

Currently you have two options for Package Dependency version constraints: >= or ==
I propose VIPM should use or allow Semantic versioning.  That way, if a dependency package has a breaking change, the dependent package can know that it is not compatible with the updated version.  This is a big missing piece to VIPM's dependency management, since it currently assumes that a package will forever be able to support future versions of all dependencies, which simply is not the case in real life, as breaking changes do happen from time to time.  Allowing for semantic versioning will help identify and prevent breaking code.

Edited November 14, 2020 by Steven Dusing
updated reasoning for the feature

[Jim Kring]

Great suggestion, Steven, and one that we're looking into! It gets my vote.

[sowthri]

Hi,

Please refer the below blog. You may have an idea on Semantic Versioning.
https://www.meritedin.com/robust-api.html

Please don't forget to take a look on the videos listed on their playlist.

[sowthri]

Hi,

Please refer the below blog. You may have an idea on Semantic Versioning.
https://www.meritedin.com/robust-api.html

Please don't forget to take a look on the videos listed on their playlist.