Upgrade UniFFI to 0.27.3 #379
Merged
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
tnull
force-pushed
the
2024-10-upgrade-uniffi
branch
3 times, most recently
from
809bccc to
4aaa01d
Compare
|
Need to resolve conflict! |
tnull
force-pushed
the
2024-10-upgrade-uniffi
branch
from
4aaa01d to
d0a14d2
Compare
Rebased to resolve minor conflict. |
G8XSU
approved these changes
Oct 16, 2024
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.
We bump our
uniffidependencies to 0.27.3 to get the newer features (mostly async trait support, really).We don't go to 0.28 directly since it breaks our Swift build process (I kinda assume we'll have to switch to the newly introduced
uniffi-bingend-swiftbinary, but we'll see).