Skip to content

Fix builds to not probe Maven for 1000.0.0 versioned artifacts (#58425) - #58425

Closed
coado wants to merge 1 commit into
react:mainfrom
coado:@coado/maven-probe-fix
Closed

Fix builds to not probe Maven for 1000.0.0 versioned artifacts (#58425)#58425
coado wants to merge 1 commit into
react:mainfrom
coado:@coado/maven-probe-fix

Conversation

@coado

@coado coado commented Sep 9, 2026

Copy link
Copy Markdown
Contributor

Summary:
Fixes issue with probing Maven Central repo for artifacts with version 1000.0.0 which are not stored there. The reason is that it creates most of the traffic on Maven Mirror that is forwarded to Maven Central due to artifacts not being cached because they are not found. After this change:

  • Gradle retains its existing dependency substitutions and forced versions.
  • Local file-based Maven repositories may still provide 1000.0.0 artifacts.
  • CocoaPods continues falling back to building React Native from source.
  • SwiftPM retains its existing 1000.0.0 → nightly resolution behavior.
  • Published React Native and Hermes versions continue to be queried normally.

Changelog:

[GENERAL][FIXED] - Changed builds to not probe Maven for 1000.0.0 versioned artifacts.

Test Plan:
Ran pod install and build the HelloWorld workspace:

[MavenProbe] SKIP https://repo.reactnative.dev/maven2/.../1000.0.0/...reactnative-dependencies-debug.tar.gz
[MavenProbe] SKIP https://repo1.maven.org/maven2/.../1000.0.0/...reactnative-dependencies-debug.tar.gz
[ReactNativeDependencies] No prebuilt artifacts found, reverting to building from source.

[MavenProbe] SKIP https://repo.reactnative.dev/maven2/.../1000.0.0/...reactnative-core-debug.tar.gz
[MavenProbe] SKIP https://repo1.maven.org/maven2/.../1000.0.0/...reactnative-core-debug.tar.gz
[ReactNativeCore] No prebuilt artifacts found, reverting to building from source.

Pod installation complete! There are 85 dependencies from the Podfile and 84 total pods installed.

Ran SwiftPM setup on a disposable copy of HelloWorld and built the generated Xcode project.

[setup-apple-spm] React Native version: 1000.0.0
[download-spm-artifacts] Detected dev version (1000.0.0), resolving as nightly...
[download-spm-artifacts] Resolved nightly: 0.89.0-nightly-20260909-b830082cf

[MavenProbe] HEAD https://repo.reactnative.dev/maven2/.../0.89.0-nightly-20260909-b830082cf/...reactnative-core-debug.tar.gz
[MavenProbe] HEAD https://repo.reactnative.dev/maven2/.../0.89.0-nightly-20260909-b830082cf/...reactnative-dependencies-debug.tar.gz

Published react-android:1000.0.0 to /tmp/maven-local, then ran the repository’s real HelloWorld Android build and a verbose Gradle rebuild.

[MavenProbe] SKIP remote Maven https://repo.reactnative.dev/maven2 for React Native 1000.0.0
[MavenProbe] SKIP remote Maven https://repo.maven.apache.org/maven2/ for React Native 1000.0.0

During the HelloWorld build:

[MavenProbe] SKIP remote Maven https://repo.maven.apache.org/maven2/ for React Native 1000.0.0
[MavenProbe] SKIP remote Maven https://dl.google.com/dl/android/maven2/ for React Native 1000.0.0
[MavenProbe] SKIP remote Maven https://www.jitpack.io for React Native 1000.0.0

BUILD SUCCESSFUL in 5s

Reviewed By: cipolleschi

Differential Revision: D119646843

Pulled By: coado

@meta-cla meta-cla Bot added the CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. label Sep 9, 2026
@facebook-github-tools facebook-github-tools Bot added p: Software Mansion Partner: Software Mansion Partner p: Facebook Partner: Facebook labels Sep 9, 2026
@meta-codesync

meta-codesync Bot commented Sep 11, 2026

Copy link
Copy Markdown

@coado has imported this pull request. If you are a Meta employee, you can view this in D119646843.

…ct#58425)

Summary:
Fixes issue with probing Maven Central repo for artifacts with version `1000.0.0` which are not stored there. The reason is that it creates most of the traffic on Maven Mirror that is forwarded to Maven Central due to artifacts not being cached because they are not found. After this change:
- Gradle retains its existing dependency substitutions and forced versions.
- Local file-based Maven repositories may still provide 1000.0.0 artifacts.
- CocoaPods continues falling back to building React Native from source.
- SwiftPM retains its existing 1000.0.0 → nightly resolution behavior.
- Published React Native and Hermes versions continue to be queried normally.

## Changelog:

[GENERAL][FIXED] - Changed builds to not probe Maven for `1000.0.0` versioned artifacts.


Test Plan:
Ran `pod install` and build the HelloWorld workspace:

```
[MavenProbe] SKIP https://repo.reactnative.dev/maven2/.../1000.0.0/...reactnative-dependencies-debug.tar.gz
[MavenProbe] SKIP https://repo1.maven.org/maven2/.../1000.0.0/...reactnative-dependencies-debug.tar.gz
[ReactNativeDependencies] No prebuilt artifacts found, reverting to building from source.

[MavenProbe] SKIP https://repo.reactnative.dev/maven2/.../1000.0.0/...reactnative-core-debug.tar.gz
[MavenProbe] SKIP https://repo1.maven.org/maven2/.../1000.0.0/...reactnative-core-debug.tar.gz
[ReactNativeCore] No prebuilt artifacts found, reverting to building from source.

Pod installation complete! There are 85 dependencies from the Podfile and 84 total pods installed.
```

Ran SwiftPM setup on a disposable copy of HelloWorld and built the generated Xcode project.

```
[setup-apple-spm] React Native version: 1000.0.0
[download-spm-artifacts] Detected dev version (1000.0.0), resolving as nightly...
[download-spm-artifacts] Resolved nightly: 0.89.0-nightly-20260909-b830082cf

[MavenProbe] HEAD https://repo.reactnative.dev/maven2/.../0.89.0-nightly-20260909-b830082cf/...reactnative-core-debug.tar.gz
[MavenProbe] HEAD https://repo.reactnative.dev/maven2/.../0.89.0-nightly-20260909-b830082cf/...reactnative-dependencies-debug.tar.gz
```

Published `react-android:1000.0.0` to `/tmp/maven-local`, then ran the repository’s real HelloWorld Android build and a verbose Gradle rebuild.

```
[MavenProbe] SKIP remote Maven https://repo.reactnative.dev/maven2 for React Native 1000.0.0
[MavenProbe] SKIP remote Maven https://repo.maven.apache.org/maven2/ for React Native 1000.0.0
```

During the HelloWorld build:

```
[MavenProbe] SKIP remote Maven https://repo.maven.apache.org/maven2/ for React Native 1000.0.0
[MavenProbe] SKIP remote Maven https://dl.google.com/dl/android/maven2/ for React Native 1000.0.0
[MavenProbe] SKIP remote Maven https://www.jitpack.io for React Native 1000.0.0

BUILD SUCCESSFUL in 5s
```

Reviewed By: cipolleschi

Differential Revision: D119646843

Pulled By: coado
@meta-codesync meta-codesync Bot changed the title Fix builds to not probe Maven for 1000.0.0 versioned artifacts Fix builds to not probe Maven for 1000.0.0 versioned artifacts (#58425) Sep 11, 2026
@coado
coado force-pushed the @coado/maven-probe-fix branch from 6e1169c to 2dc1f05 Compare September 11, 2026 10:47
@meta-codesync

meta-codesync Bot commented Sep 11, 2026

Copy link
Copy Markdown

@coado has exported this pull request. If you are a Meta employee, you can view the originating Diff in D119646843.

@meta-codesync meta-codesync Bot closed this in b5c1522 Sep 11, 2026
@meta-codesync meta-codesync Bot added the Merged This PR has been merged. label Sep 11, 2026
@meta-codesync

meta-codesync Bot commented Sep 11, 2026

Copy link
Copy Markdown

@coado merged this pull request in b5c1522.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. Merged This PR has been merged. meta-exported p: Facebook Partner: Facebook p: Software Mansion Partner: Software Mansion Partner

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant