Bump deployment target to iOS 15.0 #780
Draft
Conversation
This file contains 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
Both current known consumers of the library target iOS 15 and upwards. This, unfortunately, introduced various deprecation warnings. Fixing them is out of scope at the moment, given the possibility that soon some of the affected classes will be removed as part of a UX refresh.
1 task
|
Oh no, those warnings failed CI build.
|
mokagio
changed the title
|
@crazytonyli thank you for checking! 😳 ouch... 🤔 I like how our pod validation doesn't allow warnings. So, I think it might be best to bench this PR. As per the PR description, I don't think it's worth spending time on those warnings at the moment:
What do you think? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What it says in the title.
Both current known consumers of the library target iOS 15 and upwards.
This, unfortunately, introduced various deprecation warnings. Fixing them is out of scope at the moment, given the possibility that soon some of the affected classes will be removed as part of a UX refresh.
CHANGELOG.mdif necessary.