Initial investigation finished:
Common solution is to provide wide version range for dependencies - never fixed version as this will cause conflicts for others.

However we cannot really say and test many use cases as our modules are now linked as development pods:

When conflict happens it's it's usually because invalid version ranges:

[!] CocoaPods could not find compatible versions for pod "Alamofire":

  In Podfile:

    AGSCore (from `../modules/core`) was resolved to 1.0.0, which depends on

      Alamofire (= 4.6.0)

    Alamofire (< 4.5)

Going to adjust ranges in PR.