[0.88.0-rc.1] Test Report #1420

Target Minor

0.88

Under what system configuration was the test run?

Not captured at the time. This report is a retroactive record, see the note below.

Tested configurations

Refer to this spreadsheet for test cases.

• RNTester + iOS + Hermes
• RNTester + Android + Hermes
• RNTestProject + iOS + Hermes
• RNTestProject + Android + Hermes

Close this issue if there are no blocking issues.

Blocking Issues?

• None. 0.88.0-rc.1 was published on 2026-09-15.

Note: retroactive record

Backfilled alongside #1419 so the 0.88 series has the reports the process requires. Per the testing guide, manual testing is required for RC0, RC1, the golden RC and stable, so rc.1 needs one as well as rc.0. The four dimensions are recorded as covered per the release captain; per-case notes and system configuration from the original session were not captured.

What shipped in rc.1

12 commits between the two tags, notably the React 19.3.0 sync (#58446), the EventTarget dispatch work (#58450, #58479), the SPM chain (#58290, #58362, #58379), the codegen crawl fix (#58518) and the Hermes bump to 260318099.0.3.

CI state on the release commit

Test All was green on the v0.88.0-rc.1 commit apart from the known test_js failure, which was the same structural cache-key-test.js problem described in #1419 and was fixed later that day in ad7b17d8eef.

Two template e2e issues were found and resolved during this RC rather than after it:

• the template's react pin lagged the 19.3.0 sync, causing ERESOLVE across all four template e2e jobs. Fixed in react-native-community/template on its 0.88-stable branch, which the e2e clones at run time, so a rerun picked it up with no RN commit needed.
• post_publish failed on its 3-minute "Verify Release is on NPM" timeout. The publish itself succeeded; this is npm propagation lag, not a release failure.