540 Commits
Author SHA1 Message Date
Riccardo Cipolleschi 00ac282959 [LOCAL] fix linting 2026-07-24 15:57:34 +01:00
Riccardo Cipolleschi 6766cc3655 Update repository references on 0.86 (#57666) 2026-07-24 15:51:16 +01:00
Riccardo Cipolleschi 5b9e949a5a Backport npm trusted publishing to 0.86 (#57664) 2026-07-24 13:57:46 +01:00
Gabriel Donadel Dall'Agnol 27931ffc9c Fix Android template E2E for PRs targeting stable branches (#57650)
On pull_request events github.ref_name is "<pr-number>/merge", which never
matches *-stable*, so the template E2E always cloned the template's main
branch. Template main now ships a Gradle 9.4.1 wrapper (bundling Kotlin
2.3.0), whose metadata the Kotlin 2.1.0 compiler used by
@react-native/gradle-plugin on 0.86 cannot read, breaking
:gradle-plugin:settings-plugin:compileKotlin on every PR to 0.86-stable.

Use github.base_ref (set on PR events) so PRs targeting stable branches
check out the matching template branch, falling back to ref_name for
branch pushes.
2026-07-23 20:18:19 +02:00
Fabrizio Cucci a8eb4f70c7 Unbreak android CI by moving to ubuntu-latest (#57216)
Backport of #57216 to 0.86-stable.

Move CI jobs off the timing-out 4-core-ubuntu / 8-core-ubuntu runners
to ubuntu-latest across the Android, fantom, build and publish
workflows. macOS runners are unchanged.

This is the equivalent of upstream commit
097dbc288b8f803caea324ae9522f0262b300a07; applied manually because the
workflow files have diverged on this branch and a direct cherry-pick
conflicts.
2026-06-16 15:15:31 +01:00
Fabrizio Cucci 1e1fd4fbf3 Update GH Actions references from facebook/react-native to react/react-native (#57167)
Backport of #57167 to 0.86-stable.

Update GitHub Actions workflow fork-prevention guards
(github.repository == ...) and the monitor-new-issues repo_owner
parameter to reflect React Native's migration from
facebook/react-native to react/react-native.

This is the equivalent of upstream commit
861d8e07a027cabddc80580ca4311aab40c4dd26; applied manually because the
workflow files have diverged on this branch and a direct cherry-pick
conflicts.
2026-06-16 10:02:11 +01:00
Riccardo Cipolleschi 0518d72c0e Add E2E test retry jobs for PRs to handle flakiness (#56581)
Summary:
- Adds retry jobs (up to 2 retries) for all 4 E2E test jobs on PRs to handle flakiness
- Original E2E jobs use `continue-on-error` on PRs so failures don't block the workflow; on `main`, behavior is unchanged and the existing `rerun-failed-jobs` mechanism continues to work
- Each retry runs on a fresh runner (addressing environment-level flakes) and is triggered via step-level outcome captured as a job output
- Added `overwrite: true` to artifact uploads in maestro composite actions so retry jobs don't conflict on artifact names

### How it works
- **On PRs:** E2E job fails → `retry_1` triggers → if that fails → `retry_2` triggers. All have `continue-on-error` so the workflow stays green.
- **On `main`:** `continue-on-error` is `false`, retry jobs are skipped (PR-only), and `rerun-failed-jobs` handles retries as before.

### Known limitation
Since these are matrix jobs (Debug/Release), the job output uses the last-to-complete matrix combination's value. If only one flavor fails and the passing one finishes last, the retry may not trigger. In the common flakiness pattern (environment-level issues), both flavors tend to be affected, so this works well in practice.

## Changelog:
[Internal] - Add E2E test retry jobs for PRs

Pull Request resolved: https://github.com/facebook/react-native/pull/56581

Test Plan:
- CI will validate the workflow syntax
- On a PR where E2E tests pass: retry jobs should be skipped
- On a PR where E2E tests fail due to flakiness: retry jobs should trigger and (ideally) pass on a fresh runner
- On pushes to `main`: existing `rerun-failed-jobs` behavior is preserved (retry jobs are skipped)

Reviewed By: cortinico

Differential Revision: D102327900

Pulled By: cipolleschi

fbshipit-source-id: e257e012357fdba442c302085ceed0667355272e
2026-04-27 04:18:19 -07:00
Jakub Piasecki 46c0177162 Change failing C++ api validation signal to blocking (#56503)
Summary:
Pull Request resolved: https://github.com/facebook/react-native/pull/56503

Changelog: [Internal]

Changes the signals pointing out C++ api snapshot not being updated to be blocking.

Commits the new baseline snapshots

Reviewed By: cipolleschi, cortinico

Differential Revision: D101617655

fbshipit-source-id: 8836cb55292ab2e3fa0b696d289f9bd0daf46dec
2026-04-20 06:03:05 -07:00
Riccardo Cipolleschi 8043a6dfb7 Validate NPM token before nightly publish (#56502)
Summary:
Pull Request resolved: https://github.com/facebook/react-native/pull/56502

Adds an NPM token validation step to the `build_npm_package` job of the
React Native nightly workflow. Mirrors the same check we recently added
to `create-release.yml` and the Hermes `rn-build-hermes.yml` workflows
so we fail fast (with a clear message) instead of failing partway
through the publish step when the token is expired or missing.

## Changelog:
[Internal] -

Reviewed By: fabriziocucci

Differential Revision: D101594276

fbshipit-source-id: bb0fbddf5eba921f4184117dc29c7cc9e911a00e
2026-04-20 03:19:02 -07:00
Riccardo Cipolleschi 0223364b43 Validate NPM token before creating a release (#56501)
Summary:
Pull Request resolved: https://github.com/facebook/react-native/pull/56501

Add an early NPM token validation step to the create-release workflow.
This runs `npm whoami` right after checkout to fail fast if the token is
expired or invalid, avoiding wasted CI time on a release that would fail
at the publish step.

The step gracefully skips when no token is present (e.g. fork PRs).

## Changelog:
[Internal] -

Reviewed By: christophpurrer

Differential Revision: D101377190

fbshipit-source-id: 53243a24649f86d274b2ea31793333fd815e69cb
2026-04-20 02:51:18 -07:00
Andrew Datsenko 7d51201292 Retry only failed Fantom tests instead of full suite on CI (#56425)
Summary:
Pull Request resolved: https://github.com/facebook/react-native/pull/56425

Changelog: [Internal]

The Fantom CI retry loop previously re-ran the entire test suite on each attempt. This wastes time and can introduce new flaky failures that weren't in the original run (e.g., a FlatList race condition appearing on attempt 2 but not attempt 1).

This changes the retry logic to use Jest's `--onlyFailures` flag on attempts 2 and 3, so only the test suites that actually failed get re-run. For example, if 1 out of 99 suites fails with a SIGSEGV, the retry runs just that 1 suite instead of all 99 — reducing retry time from ~80s to seconds.

Reviewed By: rubennorte

Differential Revision: D100618771

fbshipit-source-id: 3b311ddb6e88b8948120e9510b50212dfe79ae81
2026-04-13 07:25:34 -07:00
Dawid Małecki 0979d50262 Add CI workflow for validating C++ API snapshot (#56042)
Summary:
Pull Request resolved: https://github.com/facebook/react-native/pull/56042

Adds CI workflow for validating whether the current C++ API snapshot is equivalent with the generated one.

Changelog:
[Internal]

Reviewed By: cortinico

Differential Revision: D95963515

fbshipit-source-id: 4629999e2d09dbdcfb9fd3e6308a9254dd4f0237
2026-03-31 08:32:57 -07:00
Jakub Piasecki bf7cb8964f Remove obsolete workflows (#56172)
Summary:
Pull Request resolved: https://github.com/facebook/react-native/pull/56172

Changelog: [Internal]

Removes obsolete workflows which were testing Hermes V1 integration. Since Hermes V1 is the default now, those are no longer needed.

Reviewed By: cortinico

Differential Revision: D97464853

fbshipit-source-id: df3394548e6e1b3cf854674b2371cf31be935c81
2026-03-22 23:44:49 -07:00
Andrew Datsenko 37b6c089cb Split Fantom workflow into separate build and test jobs (#54729)
Summary:
Pull Request resolved: https://github.com/facebook/react-native/pull/54729

Changelog: [Internal]

- Created new build-fantom-runner action to compile the Fantom runner binary
- Modified run-fantom-tests action to download and use pre-built binary
- Updated test-all.yml workflow to run build and test as separate jobs
- Removed build dependencies and ccache configuration from test job

Reviewed By: cortinico

Differential Revision: D88012198

fbshipit-source-id: cd1c91b18cccc3c62b9edbcbeb131e80551369f1
2026-03-09 23:21:17 -07:00
Fabrizio Cucci 3b8455c42e Fix build_debugger_shell job by passing --prepack to yarn build (#56005)
Summary:
Pull Request resolved: https://github.com/facebook/react-native/pull/56005

Changelog: [Internal]

The build_debugger_shell CI job was failing because build-binary.js
expects pkg.main to start with ./dist/, but without --prepack the
prepack.js script never runs, so main stays as ./src/index.js.

This was caused by a series of PRs:
- PR #54857 refactored debugger-shell/package.json to use the
  publishConfig pattern, moving main from ./dist/index.js to
  ./src/index.js.
- PR #55415 added the --prepack flag to build.js to support this.
- PR #55416 added the build_debugger_shell CI job but ran yarn build
  without --prepack.

The fix passes --prepack to yarn build so that prepack.js rewrites
package.json main to ./dist/index.js before build-binary.js runs.

Reviewed By: huntie

Differential Revision: D95818417

fbshipit-source-id: 03c8340c415960c3937b13bdea3952798d2d420e
2026-03-09 12:28:25 -07:00
Alex Hunt 1f69a3972a Fix running all test-all jobs outside PRs (#55917)
Summary:
Pull Request resolved: https://github.com/facebook/react-native/pull/55917

As a defensive initial design, conditional Android/iOS job runs for `test-all` were intended to be scoped to PRs only, however required a missing `== 'true'` match specifier.

Fixing this will help us catch rare integration-conflict failures on `main`, at the appropriate commit.

Changelog: [Internal]

Reviewed By: cortinico

Differential Revision: D95042221

fbshipit-source-id: ffa23651c9b8c18939ccbd7ab2279243690944d2
2026-03-05 03:26:12 -08:00
Fabrizio Cucci d6f2b34a95 Back out "Use stable Hermes for dry-run builds on stable branches" (#55877)
Summary:
Pull Request resolved: https://github.com/facebook/react-native/pull/55877

Changelog: [Internal]

Original commit changeset: d5888a00b29c

Original Phabricator Diff: D95022571

It turns out, this didn't fix the issue.

Reviewed By: cipolleschi

Differential Revision: D95051094

fbshipit-source-id: f99ecc0b76a1bdf4ba2eb3117b08754dfbbc2558
2026-03-03 06:07:55 -08:00
Fabrizio Cucci cac978be7f Use stable Hermes for dry-run builds on stable branches (#55867)
Summary:
Pull Request resolved: https://github.com/facebook/react-native/pull/55867

Changelog: [Internal]

The build_android workflow was incorrectly using for dry-run
builds on stable branches (e.g., 0.85-stable), causing it to append  suffix
to the Hermes version. This resulted in trying to fetch non-existent SNAPSHOT artifacts
like in https://github.com/facebook/react-native/actions/runs/22592250332/job/65471130298.

This fix adds a check to detect stable branches (via github.ref_name or github.base_ref)
and uses  instead, which fetches the stable Hermes release from
Maven Central without the -SNAPSHOT suffix.

We check both github.ref_name and github.base_ref to cover two scenarios:
* ref_name: Direct pushes to stable branches (e.g. pushing to 0.85-stable)
* base_ref: Pull requests targeting stable branches (e.g. cherry-pick PRs where the source branch isn't named -stable but the target is)

Reviewed By: cipolleschi

Differential Revision: D95022571

fbshipit-source-id: d5888a00b29c9b5a22328fa794070c317671db2b
2026-03-03 04:07:14 -08:00
Riccardo Cipolleschi aefe0f59e2 Skip set-rn-artifacts-version for PRs targeting stable branches (#55809)
Summary:
When a PR targets a `-stable` branch, `github.ref_name` is the PR branch (not ending in `-stable`), so the version script was incorrectly running. Added a check for `github.base_ref` to also skip the script when the PR target branch is a stable branch.

## Changelog:
[Internal] - Skip set-rn-artifacts-version for PRs targeting stable branches

Pull Request resolved: https://github.com/facebook/react-native/pull/55809

Test Plan: CI should pass without running the artifacts version script on PRs targeting stable branches.

Reviewed By: cortinico

Differential Revision: D94678295

Pulled By: cipolleschi

fbshipit-source-id: 5809ec710c191075f1bc1528ecff95f8bd745257
2026-03-02 05:21:32 -08:00
Nicola Corti 79182c2d29 Explicitely set REACT_NATIVE_DOWNLOADS_DIR to use predownloaded deps (#55567)
Summary:
This updates the CI to use `REACT_NATIVE_DOWNLOADS_DIR` so the directory where the C++ dependencies are consumed from is always the same.

This works in conjuction with:
- https://github.com/react-native-community/docker-android/pull/248

## Changelog:

[INTERNAL] -

Pull Request resolved: https://github.com/facebook/react-native/pull/55567

Test Plan: CI

Reviewed By: cipolleschi

Differential Revision: D93417423

Pulled By: cortinico

fbshipit-source-id: 75664e7d48cbba2483e05c023ac0201fb768ef35
2026-02-16 08:05:19 -08:00
Nicola Corti 9e49b37588 Set LC_ALL: C.UTF8 to further jobs to unblock nightly (#55564)
Summary:
This reapplies the same changes from https://github.com/facebook/react-native/issues/55453 to further jobs that were missing it.
This should unblock nightlies that are currently failing.

## Changelog:

[INTERNAL] -

Pull Request resolved: https://github.com/facebook/react-native/pull/55564

Test Plan: CI

Reviewed By: cipolleschi

Differential Revision: D93408173

Pulled By: cortinico

fbshipit-source-id: 11823daeb8ef95fb5b9b8942f23f33353b6d6b6b
2026-02-16 04:49:33 -08:00
Alex Hunt 3f200a237c Add conditional Android/iOS job runs in test-all workflow (#55449)
Summary:
Pull Request resolved: https://github.com/facebook/react-native/pull/55449

Further workflow optimisation after D92417918. Aims to improve speed of CI signals and reduce costs by excluding Android and iOS specific jobs when a PR contains changes exclusively within native code to one platform.

Changelog: [Internal]

Reviewed By: NickGerleman

Differential Revision: D92512983

fbshipit-source-id: feb67ce140014352219ae2b5720fc819ec5e1c11
2026-02-16 04:48:24 -08:00
Nicola Corti 319e589d3d Bump Gradle to 9.3.1 (#55453)
Summary:
This advances our Gradle version to the latest stable

## Changelog:

[ANDROID] [CHANGED] - Gradle to 9.3.1

Pull Request resolved: https://github.com/facebook/react-native/pull/55453

Test Plan: CI

Reviewed By: cipolleschi

Differential Revision: D92529174

Pulled By: cortinico

fbshipit-source-id: 252ed969e9198758cfe69dc74bb69e2a5c50a347
2026-02-10 07:41:08 -08:00
Emily Brown 1ff071544e Align with GH Actions namings (#55469)
Summary:
Pull Request resolved: https://github.com/facebook/react-native/pull/55469

Rename workflow job IDs from kebab-case to snake_case and update workflow name to match convention.

Changelog: [General][Changed] - rename workflow job IDs from kebab-case to snake_case

Reviewed By: huntie

Differential Revision: D92697078

fbshipit-source-id: bc8c99b6807997fe625d1f7921b3664992697b36
2026-02-09 08:19:37 -08:00
Alex Hunt fe6d80d85c Update run_fantom_tests to depend on lint (#55448)
Summary:
Pull Request resolved: https://github.com/facebook/react-native/pull/55448

Changelog: [Internal]

Reviewed By: cipolleschi

Differential Revision: D92512982

fbshipit-source-id: ac13bf6f814cf612f94891057a27bb2820ea8c7e
2026-02-06 10:05:53 -08:00
Emily Brown b79cd8d247 Remove Danger.js workflow and React native bots package (#55385)
Summary:
Pull Request resolved: https://github.com/facebook/react-native/pull/55385

Now that all Danger.js checks have been migrated to native GitHub Actions in the `annotate-pr.yml` workflow, this removes the deprecated Danger infrastructure:

- Deletes `.github/workflows/danger-pr.yml` workflow
- Deletes `private/react-native-bots/dangerfile.js`
- Removes `danger` npm dependency from `react-native-bots/package.json`

The functionality previously provided by Danger.js is now handled by:
- **API diff detection**: `diff-js-api-changes` action
- **PR body validation**: `validatePRBody.js` script (summary, test plan, changelog checks)
- **Branch targeting**: `checkBranchTarget.js` script (validates target branch, adds "Pick Request" label)
- **PR commenting**: `post-pr-comment` action

This simplifies the CI pipeline by removing the third-party Danger dependency and consolidating PR annotation logic into maintainable GitHub Actions workflows.

Changelog: [Internal]

Reviewed By: huntie

Differential Revision: D91695886

fbshipit-source-id: c88001ef75d16c4709c7972add141db0df3b5a30
2026-02-06 08:14:53 -08:00
Emily Brown 1ee6fdc571 Add branch targeting check to analyze-pr workflow (#55383)
Summary:
Pull Request resolved: https://github.com/facebook/react-native/pull/55383

Adds a branch targeting validation that replaces the equivalent Danger.js check.
  The check validates that PRs target either `main` or a `-stable` branch, and
  automatically adds the "Pick Request" label when targeting stable branches.

  - Created `checkBranchTarget.js` - pure function returning validation message
  - Added check step to `annotate-pr.yml` that calls the JS and adds labels
  - Added `issues: write` permission for label functionality

Changelog: [Internal]

Reviewed By: huntie

Differential Revision: D91685081

fbshipit-source-id: 87e7124f7d825b51cb791dc94720c487ff95d414
2026-02-06 08:14:53 -08:00
Emily Brown 5e41043fb5 Add PR body validation to analyze-pr workflow (#55382)
Summary:
Pull Request resolved: https://github.com/facebook/react-native/pull/55382

This adds a `validatePRBody.js` script that checks pull request descriptions for required sections as part of a new `analyze-pr.yml` workflow that will replace part of the Danger-pr workflow.

The validation includes:
- **Description length check**: Fails if the PR body is missing or less than 50 characters
- **Summary section check**: Warns if the PR lacks a "## Summary" section
- **Test plan check**: Warns if the PR lacks a "## Test Plan" section
- **Changelog validation**: failing if missing or invalid

Key behaviors:
- Phabricator-sourced PRs (detected via "Differential Revision:" in body) skip summary, test plan, and changelog validation since these are enforced differently
- Validation messages use GitHub's `[!WARNING]` and `[!CAUTION]` callout syntax for clear visual feedback
- The workflow fails (via `core.setFailed`) when any required check fails
- Messages are passed to `postPRComment` alongside API changes for consolidated PR comments

This aims to mimic relevant parts of dangerfile.js

Changelog: [Internal]

Reviewed By: huntie

Differential Revision: D91158803

fbshipit-source-id: 2304251d18f9fc8bf9a29e536fff2d979573bd86
2026-02-06 08:14:53 -08:00
Emily Brown 6a9d792f9a Add api-changes.yml workflow to replace danger-pr (#55341)
Summary:
Pull Request resolved: https://github.com/facebook/react-native/pull/55341

Changelog:
[INTERNAL] [CHANGED] - Add api-changes.yml workflow to replace danger-pr for detecting changes in the js api

  The workflow:
  - Triggers on `pull_request_target` for opened, edited, reopened, and synchronize events
  - Checks out the main branch (for security, using trusted code)
  - Runs the `diff-js-api-changes` action to detect API changes
  - Posts a PR comment using the generic `post-pr-comment` action

  The PR comment script creates, updates, or deletes a bot comment based on whether
  there are any sections to report, using a marker to identify existing bot comments.

Reviewed By: huntie

Differential Revision: D90991845

fbshipit-source-id: 753475a7c24df8bc581b2ab47bfad1f5551c823c
2026-02-06 08:14:53 -08:00
Alex Hunt b2b446e711 Apply path filtering checks to test-all workflow (#55429)
Summary:
Pull Request resolved: https://github.com/facebook/react-native/pull/55429

Completes this stack of diffs focused around the organisation and efficiency of the `test-all` GitHub Actions workflow.

**Changed**

All root jobs (excluding `lint`), when running against a PR, now depend on the initial `check_code_changes` job. This matches any non-Markdown, non docs change — meaning trivial PRs such as changelog updates should now avoid unnecessarily running the expensive parts of this workflow.

IMPORTANT: This is a significant change at the root of the workflow that contributes to our prebuilts/release infra — please review carefully.

**The new `any_code_change` filter**

Extremely defensive:
- Matches `'!**/__docs__/**', '!**/*.md'` only.
- Also **always** sets `any_code_change` to true if on `main`, a release branch, or on a workflow dispatch (`github.event_name != 'pull_request'`).

Changelog: [Internal]

Reviewed By: cortinico

Differential Revision: D92417918

fbshipit-source-id: ca5bc41a3c11569b8f69062ab66eeeab89d30089
2026-02-06 04:25:32 -08:00
Alex Hunt e0935e645d Update test_js job to be dependent on lint (#55428)
Summary:
Pull Request resolved: https://github.com/facebook/react-native/pull/55428

With a lighter weight `lint` job, make this blocking for `test_js` runs. The combined `lint` + `test_js` execution time in series remains far less than the native build+test jobs.

Changelog: [Internal]

Reviewed By: cortinico

Differential Revision: D92417805

fbshipit-source-id: 05832257518c8141ca0955f18e740f752e675d4d
2026-02-05 11:06:06 -08:00
Alex Hunt 7e752341bd Collapse lint action into test-all workflow (#55427)
Summary:
Pull Request resolved: https://github.com/facebook/react-native/pull/55427

Following previous diffs, this now promotes the `lint` action to direct job steps.

**Motivation**

This has the advantage of making sub-steps in the GitHub UI visible, rather than running the 7 lint steps under a single banner.

I feel this is justified in the case of `lint`, although increasing the size of `.github/workflowsl/test-all.yml` slightly, because:
- Each step in this job is a distinct tool run with differing output, rather than one logical "action" — and this grouped output is therefore useful to the user.
- Lint failures are reasonably frequent for users, emphasising the above.

Changelog: [Internal]

Reviewed By: cortinico

Differential Revision: D92417807

fbshipit-source-id: ed24cfa2e581a528e80faec4128d280926f56613
2026-02-05 11:06:06 -08:00
Alex Hunt 7112c5fd7a Split build_js_types from lint action (#55426)
Summary:
Pull Request resolved: https://github.com/facebook/react-native/pull/55426

Changelog: [Internal]

Reviewed By: cortinico

Differential Revision: D92417806

fbshipit-source-id: d7729d9589944579bf9cb1b592183f3e38a4c0c8
2026-02-05 11:06:06 -08:00
Alex Hunt ce0658155b Delete outdated check_license script (#55425)
Summary:
Pull Request resolved: https://github.com/facebook/react-native/pull/55425

See blame — this script lints for a `"PATENTS"` string inside any Git changes, which should not occur any more.

> D7119356 (8 years ago)
>
> [react-native][PR] Check PATENTS does not creep into files
>
> Summary:
> Some files have crept into the repo with the old license header. These are usually from PRs that were opened prior to the re-licensing of the project.

Changelog: [Internal]

Reviewed By: cortinico

Differential Revision: D92417808

fbshipit-source-id: 36e3507f835fe5df99644eb1a47cdc60fa68f88c
2026-02-05 11:06:06 -08:00
Alex Hunt 19305299bd Delete unused code-analysis script (#55421)
Summary:
Pull Request resolved: https://github.com/facebook/react-native/pull/55421

Deletes the largely unused `analyze_code`/`code-analysis-bot` script, which was part of our earlier CircleCI infra.

**Motivation**

- **Security**: Removes another use of a `GITHUB_TOKEN` env var being loaded into a script in our CI (similar to S603729).
- **Cleanup**: This script attempted to read various lint job results (including google-java-format, which is no longer present), and post a GitHub PR comment for >5 issues. In a GitHub Actions world, we don't really need this functionality.

**Other changes**

- The `yarn shellcheck` run from this script was load bearing, and is moved directly into the `lint` action.

Changelog: [Internal]

Reviewed By: cipolleschi

Differential Revision: D92407627

fbshipit-source-id: ef5664a273ad4aac721dbb53de73f2b96b47d75b
2026-02-05 10:02:20 -08:00
Alex Hunt ab36cdc553 Add build_debugger_shell check to CI (#55416)
Summary:
Pull Request resolved: https://github.com/facebook/react-native/pull/55416

Adds a `build_debugger_shell` job as part of the `test-all` workflow, adding missing coverage to `scripts/debugger-shell/build-binary.js`. This was broken recently by https://github.com/facebook/react-native/pull/54857.

Changelog: [Internal]

Reviewed By: cipolleschi

Differential Revision: D92396626

fbshipit-source-id: dda9427a936c46ec74821c10a8578c8a299890e9
2026-02-05 10:02:20 -08:00
Alex Hunt a25049b8dd Remove build package.json dirty state check (#55420)
Summary:
Pull Request resolved: https://github.com/facebook/react-native/pull/55420

After https://github.com/facebook/react-native/pull/54857 (use of the "publishConfig" field), this check is no longer necessary, since `yarn build` will no longer make changes to any checked in files.

In the (expectedly) rare case that `yarn build --prepack` changes are committed (only intended for CI), Flow will also fail independently.

Changelog: [Internal]

Reviewed By: cipolleschi

Differential Revision: D92397786

fbshipit-source-id: 872cc91b62295cdb6d8c2799cffb8a4cadc4106e
2026-02-05 09:14:33 -08:00
Emily Brown 3782e939df Fix diff-js-api-changes to compare PR head vs merge base (#55245)
Summary:
Pull Request resolved: https://github.com/facebook/react-native/pull/55245

Changelog: [INTERNAL] [FIXED] - Fix diff-js-api-changes workflow to correctly compare PR head vs merge base

The `diff-js-api-changes` action was comparing main to main instead of comparing the PR head to the point of main it branched from.

The workflow now:
1. Checks out main in `danger-pr.yml` to get the trusted scripts
2. Fetches the PR head commit and computes the merge base (the point it branched from main)
3. Extracts the API snapshots from both refs using `git show` to read-only temp files
4. Runs main's diff script to compare the two snapshots

**Security notes:**
- `git fetch` only downloads git objects, it does not modify the working directory
- `git show <sha>:path` extracts a file as read-only data, not executable code
- All executed scripts come from main (trusted), PR content is only used as data
- The PR's `.d.ts` file is written to a temp directory and passed as input to main's diff script

Reviewed By: huntie

Differential Revision: D90978905

fbshipit-source-id: fc9b420a27c84f1812b436f41d3169fad4f91291
2026-01-29 09:29:19 -08:00
Fabrizio Cucci ef10ac0c2e Fix bump of Podfile.lock after release (#55232)
Summary:
Pull Request resolved: https://github.com/facebook/react-native/pull/55232

Changelog: [Internal]

As suggested by cipolleschi, this is a more stable solution given that the workflow has been consistently failing for the past couple of RCs.

Reviewed By: cipolleschi

Differential Revision: D90992194

fbshipit-source-id: 7586a4bf141a875b2d780d1a359e79fc42c9ffda
2026-01-19 11:02:54 -08:00
George 0344c0c9cb fix(typo): Update JDK string version from 11 to 17 (#55167)
Summary:
Fixes a typo on the step name of `maestro-ios` gh action:

From `Set up JDK 11` -? `Set up JDK 17`

to match the actual version and be in sync with the rest of the other actions (e.g. maestro-android)

## Changelog:

<!-- Help reviewers and the release process by writing your own changelog entry.

Pick one each for the category and type tags:

[GENERAL] [FIXED] - typo on maestro ios gh action for jdk step

For more details, see:
https://reactnative.dev/contributing/changelogs-in-pull-requests

Pull Request resolved: https://github.com/facebook/react-native/pull/55167

Test Plan: No testing required

Reviewed By: cipolleschi

Differential Revision: D90688156

Pulled By: cortinico

fbshipit-source-id: d2f4ff27bd6cee18c5931ff81df5f965ddf6d01b
2026-01-14 08:53:43 -08:00
Riccardo Cipolleschi 7ed7540fa0 Use prebuilds in E2E tests (#55156)
Summary:
Now that we are using prebuilds by default in the release, we should also use prebuilds when running the E2E tests of the template app

## Changelog:
[Internal] -

Pull Request resolved: https://github.com/facebook/react-native/pull/55156

Test Plan: GHA

Reviewed By: cortinico

Differential Revision: D90673567

Pulled By: cipolleschi

fbshipit-source-id: d99c8f89f0c8737a7cb00eba654037997e661b95
2026-01-14 04:57:24 -08:00
Riccardo Cipolleschi 53337596d5 Bump Xcode to 16.4 and stop downloading Apple SDKs (#55147)
Summary:
When setting up Xcode, we also download the SDKs that is needed.
There might be cases where we can save money and time and skip the download

## Changelog:
[Internal] -

Pull Request resolved: https://github.com/facebook/react-native/pull/55147

Test Plan: GHA

Reviewed By: javache

Differential Revision: D90594740

Pulled By: cipolleschi

fbshipit-source-id: 2923d891d626dfbb8446641d37b4b3f896c1daf2
2026-01-14 03:43:05 -08:00
Rob Hogan 0cda10b00a Revert: Bump minimum Node.js version to v22.11 (prev LTS) (#55113)
Summary:
Pull Request resolved: https://github.com/facebook/react-native/pull/55113

Reverts https://github.com/facebook/react-native/pull/55038

Dropping v20 (still in LTS) causes friction with Expo's LTS policy, so we're restoring support for v20.19.

Changelog: [General][Added] Revert https://github.com/facebook/react-native/pull/55038

Reviewed By: shwanton

Differential Revision: D90467161

fbshipit-source-id: d876cf7869f11e04058f88239f553704e0706514
2026-01-11 14:30:40 -08:00
Riccardo Cipolleschi f140c4906b Use Hermes V1 as default engine (#54989)
Summary:
This change makes Hermes V1 the default engine for React Native for both platforms. This change needs to land before the branch cut of react native 0.84

bypass-github-export-checks

## Changelog:
[iOS][Changed] - Make Hermes V1 the default engine for iOS

Pull Request resolved: https://github.com/facebook/react-native/pull/54989

Test Plan:
1. Run `bundle exec pod install` and verified that Hermes V1 is used when building from source
<img height="480" alt="Simulator Screenshot - iPhone 17 Pro - 2025-12-29 at 11 28 44" src="https://github.com/user-attachments/assets/0889f16c-f2ee-4a0e-9a4d-529dd82c8283" />
2. Run `prebuild-ios -s` and verified that the scripts downloads the Hermes V1 tarball
<img width="831" height="324" alt="Screenshot 2025-12-29 at 10 37 53" src="https://github.com/user-attachments/assets/9a60565e-1e13-4967-a4a4-dd079e6b040f" />
3. GHA and nightlies

Reviewed By: vzaidman, cortinico, huntie

Differential Revision: D89881943

Pulled By: cipolleschi

fbshipit-source-id: 958b6d31bd4230ba4a5c7fee2bffc19e03dcbc89
2026-01-07 05:34:12 -08:00
Nicola Corti 9d1c55b113 Simplify the jq command used to read version inside build_android (#55057)
Summary:
This is a pick of 4cac35f7d0 inside `main`.
The commit is already on the `0.84-stable` branch.

The reasoning here is that `cat` + `jq` failed to run with:

```
Run echo "rn-version=$(cat packages/react-native/package.json | jq -r 'version')" >> $GITHUB_OUTPUT
  echo "rn-version=$(cat packages/react-native/package.json | jq -r 'version')" >> $GITHUB_OUTPUT
  shell: bash --noprofile --norc -e -o pipefail {0}
jq: error: version/0 is not defined at <top-level>, line 1:
version
jq: 1 compile error
```

I'm moving to a single `jq` invocation as it's more resilient.

## Changelog:

[INTERNAL] -

Pull Request resolved: https://github.com/facebook/react-native/pull/55057

Test Plan: N/A

Reviewed By: fabriziocucci, alanleedev

Differential Revision: D90189240

Pulled By: cortinico

fbshipit-source-id: 9b1cd6ad6d37913f8a468892cedce5f808c8c33e
2026-01-07 03:00:44 -08:00
Riccardo Cipolleschi dcfe7f50f9 Set the release version also to test RC.0 (#55054)
Summary:
This is a cherry-pick of dc90b0b7f3 on main from 0.83 and 0.84

## Changelog:

[INTERNAL] -

Pull Request resolved: https://github.com/facebook/react-native/pull/55054

Test Plan: CI

Reviewed By: cipolleschi

Differential Revision: D90174387

Pulled By: cortinico

fbshipit-source-id: 74b0ec3b853f2654ce140b9af27f13fe22c81f4a
2026-01-06 06:51:24 -08:00
Riccardo Cipolleschi 7e4fa70a12 Rerun failed fantom tests (#55053)
Summary:
Fantom tests are a bit flaky, so we are rerunning them in case they fails.

## Changelog:
[Internal] -

Pull Request resolved: https://github.com/facebook/react-native/pull/55053

Test Plan: GHA

Reviewed By: cortinico

Differential Revision: D90174181

Pulled By: cipolleschi

fbshipit-source-id: 131d6fb68a9a53eaef5b36c0f0fe9adf989219b3
2026-01-06 06:30:51 -08:00
Riccardo Cipolleschi a425f4feac Fix validate-dotslash-artifacts jobs (#55049)
Summary:
In my prs, Im seeing the validate-dotslash-artifacts job fail with the error:
```
error react-native@1000.0.0: The engine "node" is incompatible with this module. Expected version ">= 22.11.0". Got "20.19.6"
error Found incompatible module.
```

This change should fix the job by setting up a compatible version of Node

## Changelog:
[Internal] -

Pull Request resolved: https://github.com/facebook/react-native/pull/55049

Test Plan: GHA

Reviewed By: cortinico

Differential Revision: D90168396

Pulled By: cipolleschi

fbshipit-source-id: 8d81f37a62ca13d5e868869b488eec4ea36d17c7
2026-01-06 05:21:28 -08:00
Pierre Moulon 6587beab88 Fixing typos (#55047)
Summary:
Pull Request resolved: https://github.com/facebook/react-native/pull/55047

Changelog: [Internal]

Fixed typos found through comprehensive recursive scan of the react-native-github directory.

**Fixed typos:**
1. "accomodate" → "accommodate" in CHANGELOG-0.6x.md
2. "occured" → "occurred" in LaunchUtils.js
3. "compatability" → "compatibility" in 7 Renderer files
4. "recieved" → "received" in PointerEvent test files (6 instances)
5. "seperated" → "separated" in ImageExample.js

**Total: 16 typo instances fixed across 10 files**

All typos were found by scanning ~3000 text files (excluding dist/third-party/node_modules) using pattern matching for common misspellings.

Reviewed By: javache

Differential Revision: D89799362

fbshipit-source-id: 73e9123dc0bae3c1ce8e374f4752404ab7345347
2026-01-06 03:23:09 -08:00
Rob Hogan 8f10b339d4 Breaking: Bump minimum Node.js version to v22.11 (prev LTS) (#55038)
Summary:
Pull Request resolved: https://github.com/facebook/react-native/pull/55038

Bump the minimum to Node.js v22.11, which is the previous LTS now that v24 is in LTS. Drop support for Node v20.

https://nodejs.org/en/blog/release/v22.11.0
https://nodejs.org/en/about/previous-releases

Changelog: [General][Breaking] Bump minimum Node.js version to v22.11

Reviewed By: cortinico, huntie

Differential Revision: D90109056

fbshipit-source-id: 178f29d3131f21fccf956decc9ac94365a2bfe53
2026-01-05 06:21:25 -08:00