Here's an exciting one: semver is about API compatibility, but what about ABI compatibility? It's relevant with Swift!
If you try to use ReactiveSwift and ReactiveObjCBridge right now, you'll run into exciting ABI incompatibility. That's because ReactiveObjCBridge has resolved ReactiveSwift to 1.0.0, but a new adopter with ReactiveSwift ~> 1.0 will resolve to 1.1.0. The linked ReactiveObjCBridge will fail at runtime when linked into an application linking ReactiveSwift 1.1.0 (a protocol changed to a typealias, so ABI-wise, it's now a missing symbol).
So that's cool. Anyway, let's update the dependencies.
Here's an exciting one: semver is about API compatibility, but what about ABI compatibility? It's relevant with Swift!
If you try to use ReactiveSwift and ReactiveObjCBridge right now, you'll run into exciting ABI incompatibility. That's because ReactiveObjCBridge has resolved ReactiveSwift to 1.0.0, but a new adopter with
ReactiveSwift ~> 1.0
will resolve to 1.1.0. The linked ReactiveObjCBridge will fail at runtime when linked into an application linking ReactiveSwift 1.1.0 (a protocol changed to a typealias, so ABI-wise, it's now a missing symbol).So that's cool. Anyway, let's update the dependencies.