Hi @bosko.stupar,
I’m not sure this a problem specifically related to SOA but a general challenge when working in larger systems with different components, teams, deployments and so on. I don’t think there is a simple solution to this but in general, making sure to use SemVer compliant dependencies will help a lot.
Following SemVer, what you can do to reduce the problem is to establish a wider agreement on the current major version of a common shared dependency. This could be done company-wide, or per service, or per deployment unit, whatever works. Once everyone uses the same major version, there should be little conflicts as SemVer should guarantee compatibility within than boundary. Arguably, this calls for some effort and coordination when upgrading major versions, but that in the nature of new major versions which by SemVer definition will most likely contain breaking changes.