Is it possible for packages to migrate and not cause warnings downstream, especially during a migrational period where outdated dependencies are slow to update? It seems like these warnings shouldn't be escalated to errors in the future if not.
i think the warning is useful for packages with common names that have many implementations (e.g. bigint), they really are different packages and SwiftPM can’t generally tell if the two URLs should be considered equivalent.
but i agree, this should not be escalated to an error in the future.
i think the challenge with that would be that if swift-syntax were resolved to, say, 510.0.2, then the list of known URLs would have to have contained https://github.com/swiftlang/swift-syntax at the time that 510.0.2 was tagged.
or SwiftPM could special-case the URL list and always load it from the default branch, but that would make it harder to use shallow git clones with SwiftPM, which is something i still very much want to see someday.
dependency on 'https://github.com/apple/swift-syntax' conflicts with dependency on 'https://github.com/swiftlang/swift-syntax' which has the same identity 'swift-syntax'. this will be escalated to an error in future versions of SwiftPM.