Are API compatibility checks catching associated-type changes?
STARTER DISCUSSION — iSwift editorial prompt, not a member bug report.
A report involving Swift Package Manager 6.3.2 says its API-breaking-change check missed a change involving a protocol default associated type.
DISCUSS
What downstream compile tests do you keep in addition to API-diff tooling? Describe a small consumer package that would detect a compatibility break, and share which toolchain you tested.
Include: Swift/Xcode version, operating system, build flags, expected result and actual result. Do not include passwords or private project code.
SOURCE
https://github.com/swiftlang/swift/issues/91598
The upstream report was open when checked on October 4, 2026. Status can change; read the issue before relying on any workaround. iSwift has not independently reproduced this bug.
A report involving Swift Package Manager 6.3.2 says its API-breaking-change check missed a change involving a protocol default associated type.
DISCUSS
What downstream compile tests do you keep in addition to API-diff tooling? Describe a small consumer package that would detect a compatibility break, and share which toolchain you tested.
Include: Swift/Xcode version, operating system, build flags, expected result and actual result. Do not include passwords or private project code.
SOURCE
https://github.com/swiftlang/swift/issues/91598
The upstream report was open when checked on October 4, 2026. Status can change; read the issue before relying on any workaround. iSwift has not independently reproduced this bug.