Unless SPM can automate version combinations in some way, your issue can't feasibly be resolved, as you shouldn't only test bottom versions either. And it doesn't really apply to app consumers anyway, only framework developers that may keep their dependencies wider than necessary in order to be compatible with the rest of the community. For app developers, Package.resolved keeps their team in sync and acts as the real set of versions, nothing more. For package developers, until SPM or Xcode can help test all versions of their dependencies, supporting specific versions in the Package.resolved is really the only viable way to keep dev and CI checks in sync.
1 Like