Multiple packages declare targets with a conflicting name

[DrBeak1]

Describe the bug

My team just tried to update our amplfiy-swift package to 2.51.0, which seems to add opentelemetry-swift v1.15.0. This version causes a naming conflict with another package we use that depends on the DataCompression package. Recently opentelemetry-swift was updated to fix this issue, version 2.1.0 (here). Is it possible to update the version amplify-swift so it's less restrictive?

Steps To Reproduce

Steps to reproduce the behavior:
1. Create new project in Xcode
2. Add Launch Darkly SDK: https://github.com/launchdarkly/ios-client-sdk.git
3. Add `amplify-swift`
Result:
Package resolve error with "Multiple packages ..." error message.

Expected behavior

No conflicts over package dependencies.

Amplify Framework Version

2.51.0

Amplify Categories

Auth, Analytics, API

Dependency manager

Swift PM

Swift version

6.1.2

CLI version

n/a

Xcode version

16.4 and 26.0.1

Relevant log output

<details>
<summary>Log Messages</summary>


multiple packages {"datacompression", "opentelemetry-swift"} declare targets with a conflicting anme: 'DataCompression'; target names need to be unique ...

</details>

Is this a regression?

No

Regression additional context

No response

Platforms

iOS

OS Version

iOS 26

Device

iPhone 16-17

Specific to simulators

No

Additional context

No response

[harsh62]

@DrBeak1 Can you please open an issue with smithy-lang/smithy-swift repo. The dependency is defined here and they would need to update in order for you to consume it.

[DrBeak1]

@harsh62 sure thing.

[harsh62]

@DrBeak1 Will keep this issue open because once the underlying dependency updates, we will need to publish a new version too.

We will keep monitoring the smithy release, but incase we miss it, please remind us on the ticket.

[DrBeak1]

@harsh62 see comment here

[tylerjroach]

Thanks, we will work with the Smithy Swift to be ready for when this happens.

[harsh62]

@DrBeak1 Quick update here. We are still waiting for the SDK team to push out changes. Once that happens, we will also update the library.