I came up with this idea after noticing that Gradle was trying to pull react-native for @react-native-community/art from Maven, rather than from node_modules. Turns out D5542 made sure Gradle was looking for a 0.66 version (which shouldn't exist in Maven, and should only exist in node_modules), but Gradle was still checking Maven. The error Varun saw was caused by Gradle getting failures connecting to Maven due to current Maven stability issues... this diff technically "addresses" that by making sure Gradle doesn't check Maven for react-native, but there are other packages Gradle still needs from Maven and so the issues are ultimatly still occurring. So probably no reason to do this?