fix: use Gradle 9 compatible Foojay resolver on 0.83-stable#56743
fix: use Gradle 9 compatible Foojay resolver on 0.83-stable#56743WolfieLeader wants to merge 1 commit intofacebook:0.83-stablefrom
Conversation
|
Hi @WolfieLeader! Thank you for your pull request and welcome to our community. Action RequiredIn order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you. ProcessIn order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA. Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with If you have received this in error or have any questions, please contact us at cla@meta.com. Thanks! |
|
Warning JavaScript API change detected This PR commits an update to
This change was flagged as: |
|
Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Meta Open Source project. Thanks! |
Summary
Backports the Foojay resolver upgrade to
0.83-stableby changingfoojay-resolver-conventionfrom0.5.0to1.0.0.This is backwards compatible for existing projects and fixes Gradle 9 builds where Foojay 0.5.0 crashes because it references the removed
JvmVendorSpec.IBM_SEMERUfield.Why
React Native
mainalready contains the same effective fix via #56210, but the published 0.83 line still ships0.5.0. Expo SDK 55 / RN 0.83 users hit this during Android builds with Gradle 9.Refs:
Changelog:
[Android] [Fixed] - Use Gradle 9 compatible Foojay resolver convention plugin in the 0.83 Gradle plugin.
Test Plan
git diff --check@react-native/gradle-plugin@0.83.xships Foojay0.5.0and React Nativemainuses1.0.0.