Repository navigation
build(runtime): ship remaining mobile controls with v0.91.0 - #283
Merged
Merged
Conversation
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
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.
Summary
Retrom now ships the shared mobile controls for MAME Apple II+/IIe/Acorn Atom, NP2kai, PX68K, jsbeeb, Ruffle and ScummVM by pinning the matched runtime v0.91.0 release.
The official pin command verifies the host tool, both Provider chunk sets, source identity and artifact checksums together. PS2 remains outside this feature; core visibility preferences and toolbar state continue through the shared implementation.
Evidence
After: the matched v0.91.0 pairing includes their adapter layouts and the native input mappings verified in review/Play.
76dfd91b…c7de18). All nine Play samples covering the eight cores pass actual touch input and show/hide/toolbar-state checks; BBC movement and ScummVM pointer/menu clicks were visually reviewed. Manual acceptance excludes save-chain validation.Merge Danger
Door: one-way
Blast Radius: runtime
This updates the matched runtime input pin; installed Providers retain their existing upgrade-only policy, so returning to older behavior requires a forward release. No Host-specific core path or checkpoint-format migration is introduced.