docs: point the SPM snippet at the 1.x range, not 0.1.0 - #16
Merged
Merged
Conversation
`from: "0.1.0"` is a <1.0.0 requirement, so SwiftPM resolves it to 0.2.0 and never reaches the current v1.13.x tags that the release pipeline publishes. Anyone following the README verbatim silently pinned an ancient xcframework. Verified in a scratch consumer package: `from: "0.1.0"` resolves 0.2.0, `from: "1.13.0"` resolves 1.13.6, and both build. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
The README's install snippet uses
from: "0.1.0", which in SwiftPM means>=0.1.0, <1.0.0. It can never reach thev1.13.xtags the release pipeline publishes.Verified in a scratch consumer package on this host:
So anyone following the README verbatim silently pinned an ancient xcframework while believing they were on the current release. Both versions do build and link, so this is a wrong-version bug rather than a broken-install bug — the Swift SDK itself resolves and compiles fine.
🤖 Generated with Claude Code