Repository navigation
chore: update Engine to 1.0.11 for modal Glass snapshots - #59
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.
Update Engine from 1.0.10 to 1.0.11 so modal rail button images retain their original Glass appearance instead of becoming opaque gray on iOS. Pin the same version across the root package, shared Core, npm lockfile, SwiftPM, CocoaPods and Android Maven.
Engine 1.0.11 is published with the fix from webview-native-ui/engine#61. Its exact release tag passed all CI, and the published npm archive contains the reviewed capture implementation.
Validation: Maven Central Engine/Controls 1.0.11 POM/AAR downloads and checksums verified; the engine AAR runtime matches the npm package. Local build, lint, 462 unit tests and package verification pass. Independent supervisor and third-party reviews approved the dependency update. A patch release will use the existing
npm run releasescript after merge.