Repository navigation
Pin the VM to the shared Octoscript-Makepad runtime - #29
Merged
Merged
Conversation
added 6 commits
September 15, 2026 18:56
ymote
added a commit
that referenced
this pull request
Sep 19, 2026
…epad Pin the VM to the shared Octoscript-Makepad runtime
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.
Core and capabilities previously selected Makepad independently. Pin both to the Makepad revision selected by the unified Octoscript-Makepad release and update the lockfile.
Validation: 139 core tests and 127 capability tests passed. The shared AppCards/native and WASM integration checks passed.
CI note: the main branch run 35043370806 already fails formatting; this PR changes only manifests and lockfiles. Formatting failures remain in unchanged source/fuzz files. Core/capability tests, existing VM tests and locked fuzz metadata resolution passed locally. The fuzz lockfile is aligned as part of this change. No required status check is configured or bypassed.