microsoft
Suggestion: More tolerant resolving of dependencies
I have also posted this on Yammer. Please consider supporting the semantic versioning guidelines (www.semver.org) for resolving dependencies. A quick example:
I have installed BaseApp 1.0.0. I have also installed ConsumerApp that depends on BaseApp 1.0.0.
I should - imho - be able to release BaseApp 1.0.1 to my database without problems, because - following the semantic versioning - a change that only updates the "patch"-portion of the version (1.0.1) is considered to be fully backwards-compatible and therefore ConsumerApp should be allowed to run on top of BaseApp 1.0.0 aswell as o top of BaseApp 1.01 as well as any version of BaseApp 1.0.x that I have installed, as long as it's patch is higher than what app.json of ConsumerApp requires.
We are avoiding dependencies because of how clunky it is at the moment. A lot of people would be very happy if you could fix this by the next release in October.
Is there any official information on how versioning currently works with BC extensions? The official documentation on app.json doesn't provide many details.
I am currently working with base packages named like Microsoft_System_16.0.30409.0, and this isn't exactly SemVer (though it resembles major.minor.patch.build).
The resolution of this question would be very helpful for creating a reliable CI/CD.
