-
Notifications
You must be signed in to change notification settings - Fork 16
Setup Hermes V1 testing #45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Setup Hermes V1 testing #45
Conversation
9764245 to
d89a744
Compare
cipolleschi
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for working on this. I left a couple of questions
patches/hermes-v1.patch
Outdated
| "typescript": "^5.8.3" | ||
| }, | ||
| + "resolutions": { | ||
| + "hermes-compiler": "250829098.0.2" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
latest-v1 is now 250829098.0.3
Do you know if there is a way to use a specific tag instead of a version?
Otherwise, we would have to bump this every time we release a new version of Hermes.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's possible to use a tag instead of a specific version in package.json, but it needs to use the same version for the Android config.
I've added a script that will update the patch with the latest version before applying it. Is that ok?
Summary
Sets up automated testing of Hermes V1. The workflow will set up a new RN app from the template, enable Hermes V1, build the app, and run a simple E2E test using it.
E2E is based on the setup used in the React Native repository:
maestro-ios.jsmaestro-android.jsstart.ymlIf I understand the repository setup correctly, to pick up the results of the actions and show them on the website, the action needs to upload GitHub artifacts in a specific format, which I believe the new workflow does. Please correct me if I'm wrong.