Repository navigation
Keep the shared VM on the current Android-capable framework - #30
Merged
Merged
Conversation
ymote
added a commit
that referenced
this pull request
Sep 19, 2026
…epad Keep the shared VM on the current Android-capable framework
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
1 participant
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.
Align core, capabilities and both Cargo locks with the combined Makepad runtime containing current main's Android HomeIntent/build-tool support and the verified AppCard fixes. No Rust source changes. Locked fuzz metadata resolves; prior core/capability and VM suites passed. Existing unchanged formatting failures on main remain, as documented in #29; no status check is bypassed.