Repository navigation
Conversation
barhanc
marked this pull request as ready for review
November 13, 2026 10:30
This branch has not been deployed
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.
Description
Adds a consumer CI workflow to cover build and integration testing gaps tracked in #1609. It installs the published library tarball into clean apps outside the monorepo.
Regular coverage runs 13 Release app builds:
The latest regular Android cell also builds an AAB, validates it with checksum-pinned bundletool, and checks its bundled JavaScript and native libraries. Manual full coverage adds supported bare React Native/Worklets combinations, bringing the total to 45 app builds.
For #1609, this adds coverage for Linux/Windows hosts, bundled models, Android AAB packaging, iOS camera/audio build compatibility, and Expo config-plugin coexistence. EAS, OTA delivery, store upload validation, and camera/audio runtime behavior remain separate follow-ups.
Important
The workflow initially runs on relevant PRs to validate the harness. After it passes PR testing, switch regular Expo coverage to once per day (to minimize CI costs), keeping the full compatibility matrix available manually. A TODO and commented cron configuration document that follow-up. DO NOT MERGE BEFORE THAT
Introduces a breaking change?
Type of change
Tested on
Testing instructions
Screenshots
Related issues
Part of #1609
Checklist
Additional notes