Fix SwiftPM configuration by pointing to v16.2.0 instead of v16.1.3 #2284
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Thanks for proposing a pull request!
To help us review the request, please complete the following:
bug
for bug fixes)Pull Request Details
This PR fixes an issue where the SwiftPM configuration was pointing to version 16.1.3, even though the SDK had already been incremented to version 16.2.0. This would cause clients to assume version 16.2.0 had been integrated via SwiftPM when in reality version 16.1.3 was the one being linked.
Test Plan
Integrate the SDK on a sample app and verify the correct version was linked.