[swift-build-dev] Dependency consistency within package major version

Simon Pilkington simonmpilkington at icloud.com
Sat Dec 5 12:36:12 CST 2015


It looks like a module could in theory change dependencies on a minor version or patch change but only to the resolution of a major version. This is probably only going to become an issue when dependency resolution is introduced - where changing dependencies has the potential to suddenly break the consistency of a dependency graph of an unchanged consumer; are modules going to be required to stabilise their dependency graph within a major version?

Expanding on the 'Enforced Semantic Versioning’ section of the proposal doc, a dependency change could be detected and treated the same as a change in the signature of a public method but this section doesn't explicitly mention how or if dependencies will be taken into account for versioning.


More information about the swift-build-dev mailing list