fix: repair uniffi release pipeline and bump uniffi to 0.31 - #504
Merged
Conversation
… to FFM The java release job broke because unpinned cargo install pulled uniffi-bindgen-java 0.4.2, which targets uniffi 0.31 and changed its CLI. Instead of pinning backwards, move forward: - bump uniffi 0.29.5 -> 0.31.2 (segfault fix for foreign-future completion, kotlin async external-type fix) - pin uniffi-bindgen-java at 0.4.2: java bindings now use FFM instead of JNA (upstream-benchmarked 4.2x-426x faster FFI). Java artifact floor moves to Java 22 (--release 22, built on JDK 23); JNA removed from its classpath and POM. Kotlin artifact keeps JNA and stays at jvmTarget 21. - pin uniffi-bindgen-cs at gorules/uniffi-bindgen-cs@d080b41: upstream v0.11.0 (uniffi 0.31) plus the callback_interface async return-type fix (NordSecurity/uniffi-bindgen-cs#165); async custom-node handlers now generate Task<T> - assert built linux libs never require glibc above the zigbuild target, so native builds on new runners can't silently raise the floor again
ivanmiletic
approved these changes
Aug 18, 2026
uniffi 0.31 emits enum variant payload types fully qualified under the bindings package (mozilla/uniffi-rs#2698), so the android bindings reference io.gorules.zen_engine.kotlin_android.JsonBuffer even though the custom-type imports config places the class in the sibling .kotlin package. Ship a typealias in the android package so both the imported unqualified references and the newly qualified ones resolve to the same class; existing consumers keep the .kotlin package type.
Merged
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.
No description provided.