feat: Update Branch to 3.4.1 up to next major #59
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.
We were previous fuzzy pinning to 3.0.1, which for SPM works as expected (up to next major), but for CocoaPods, was limited updates to 3.0.x only. There is a new privacy manifest fix for Cocoapods in 3.4.1, so I've adjusted our fuzzy pinning to 3.4 for cocopods so it will pull in any 3.x.x release >= 3.4 (which will currently be 3.4.1) and bumped SPM to match (but used 3.4.1 because SPM has sane matching options). Unfortunately there is no way to set 3.4.1 as the min version for Cocoapods while also pinning to next major, which is why I used 3.4.
Tested in both a Cocoapods and SPM test app to see that it pulls in the correct dependencies and builds properly. No E2E required for this as SPM was already pulling in that version automatically.