Summary:
Pull Request resolved: https://github.com/facebook/react-native/pull/56683
RN's GitHub Actions CI isn't set up to authenticate against `registry.facebook.net`, causing 401s on Yarn install
As a quick fix ahead of the 0.86 cut, this manually fixes them back to `yarnpkg.com`
Changelog: [Internal]
Reviewed By: cortinico
Differential Revision: D103845323
fbshipit-source-id: d31f5bbaedfeaa35ef26837ab8faf29dbeff465e
Summary:
Bumps Metro dependency from `^0.84.2` to `^0.84.3` across all packages.
Metro 0.84.3 adds `changeId` to HMR `update-done` messages, which is required by the `unstable_fastRefreshComplete` CDP event and the Fast Refresh performance marker to deduplicate events across multiple updates for the same file change.
## Changelog:
[Internal]
Pull Request resolved: https://github.com/facebook/react-native/pull/56638
Test Plan:
- CI
cc huntie
Reviewed By: cortinico
Differential Revision: D102810175
Pulled By: motiz88
fbshipit-source-id: b05bc522fd7815f2858ce645b03bdea86a8027ea
Summary:
Pull Request resolved: https://github.com/facebook/react-native/pull/56603
Upgrade transitive dependency lodash from 4.17.21 to 4.18.1 to remediate CVE-2026-4800 (Improper Control of Generation of Code / Code Injection).
- Added `"lodash": "4.18.1"` to `resolutions` in package.json to force all lodash ranges (including `~4.17.15`) to resolve to 4.18.1
- Updated yarn.lock entry to resolve all lodash ranges to 4.18.1
Without the resolution override, the `~4.17.15` range would stay at 4.17.21 (vulnerable) since `~` only allows patch-level updates and 4.18.1 is a minor bump.
Changelog: [Internal]
Reviewed By: christophpurrer
Differential Revision: D102273666
fbshipit-source-id: d3a17ba480b5d44c048b2b1d814bc3989abcd06a
Summary:
Pull Request resolved: https://github.com/facebook/react-native/pull/56415
Reverting due to some internal applications relying on bugs in older whatwg-fetch versions.
Changelog: [Internal]
Differential Revision: D100389704
fbshipit-source-id: 93db9ec62641ea72313ad99d1a4186f8e5066e86
Summary:
Pull Request resolved: https://github.com/facebook/react-native/pull/56414
Reverting due to some internal applications relying on bugs in older whatwg-fetch versions.
Changelog: [Internal]
Differential Revision: D100389649
fbshipit-source-id: f87ed5e212508af8032e452cf2ba9836292a49d1
Summary:
Pull Request resolved: https://github.com/facebook/react-native/pull/56370
Vendor `whatwg-fetch` v3.6.20 directly into `Libraries/Network/`, replacing the npm dependency with a local copy.
`whatwg-fetch` has not had a release since December 2023 and appears to be [unmaintained](https://github.com/JakeChampion/fetch/issues/1482), by download numbers `react-native` is the dominant consumer (all this is unsurprising, since `fetch` is natively implemented in every browser).
It has several shortcomings we (with the OSS community) could improve on - one important one being that `whatwg-fetch`'s `fetch()` does not resolve immediately on receipt of headers, only on completion.
This takes the single source file from the `whatwg-fetch` npm package as `Libraries/Network/whatwg-fetch.js`, and its accompanying types, marking as originally vendored from whatwg-fetch v3.6.20 (Copyright (c) 2014-2023 GitHub, Inc., MIT license).
Changelog:
[Internal]
Reviewed By: huntie
Differential Revision: D99854694
fbshipit-source-id: 6e742c47c43d69012841671608cc8b359d20ea91
Summary:
Pull Request resolved: https://github.com/facebook/react-native/pull/56357
Bump the `package.json` minimum of `whatwg-fetch` to the latest `3.6.20`.
This version is already over two years old and was already within the `^3.0.0` range, so essentially every OSS user is already using it - as backed up by its download figures: https://www.npmjs.com/package/whatwg-fetch?activeTab=versions
Bumping for clarity ahead of vendoring 3.6.20
Changelog:
[Internal]
Reviewed By: huntie
Differential Revision: D99850877
fbshipit-source-id: 0f7754a647a26b41e02a7922de81da9d07949a4e
Summary:
Pull Request resolved: https://github.com/facebook/react-native/pull/56163
Fix CVE-2026-25896: Upgrade deep transitive dependency fast-xml-parser from 4.5.0 to 4.5.4
## Summary
Upgrading the deep transitive dependency `fast-xml-parser` from 4.5.0 to 4.5.4 in `xplat/js/react-native-github` to fix:
- CVE-2026-25896 (Incorrect Regular Expression)
Dependency chain (3 levels deep):
react-native/tester -> react-native-community/cli-platform-android -> react-native-community/cli-config-android -> fast-xml-parser@^4.4.1
The semver range `^4.4.1` naturally allows 4.5.4, so the version was nudged via temporary resolution and sticks after removal. No permanent resolution needed.
Changelog:
[General][Security] - Bumped fast-xml-parser from 4.5.0 to 4.5.4 to fix CVE-2026-25896
Reviewed By: huntie
Differential Revision: D96997931
fbshipit-source-id: 2ba65763bfb1254c581556559142bfac5450c89d
Summary:
This diff reverts D97425290
issue with this version
Depends on D97425290
Changelog: [Internal]
Reviewed By: marcoww6, panagosg7
Differential Revision: D97534385
fbshipit-source-id: b76be68b58c891ce553f96b79c3fbf157085cf08
Summary:
Pull Request resolved: https://github.com/facebook/react-native/pull/55907
Github OSS CI is failing because of D95055797.
Reverting the diff to fix the OSS CI
## Changelog:
[Internal] -
Reviewed By: lenaic
Differential Revision: D95204543
fbshipit-source-id: ef9d7b871baa00ae86bd0d619b151e5f8abc7782
Summary:
Maintainer of https://github.com/theoludwig/markdownlint-rule-relative-links/
Didn't know (until now) that this package was used by the react-native repository, and glad that you find it useful! 😄
Apparently, the package was downgraded in https://github.com/facebook/react-native/pull/50625 because of Node.js version requirement/mismatch, but now that (as far as I understand it), React Native uses Node.js v22+, it's fine to upgrade.
## Changelog:
<!-- Help reviewers and the release process by writing your own changelog entry.
Pick one each for the category and type tags:
[ANDROID|GENERAL|IOS|INTERNAL] [BREAKING|ADDED|CHANGED|DEPRECATED|REMOVED|FIXED|SECURITY] - Message
For more details, see:
https://reactnative.dev/contributing/changelogs-in-pull-requests
-->
[Internal] [Changed] - Update markdownlint-rule-relative-links to v5.1.0
Pull Request resolved: https://github.com/facebook/react-native/pull/55866
Test Plan: `lint-markdown` script still work.
Reviewed By: NickGerleman
Differential Revision: D95055797
Pulled By: cipolleschi
fbshipit-source-id: 60837b2efffdf20cf43fd9a174e40e6077f8a313
Summary:
Pull Request resolved: https://github.com/facebook/react-native/pull/55574
Upgrade the undici devDependency in react-native/dev-middleware from ^5.29.0 to ^6.23.0 to address security vulnerabilities. undici v6 drops the fastify/busboy dependency and requires Node.js >= 18, which is already satisfied by the engine requirements. The API surface used (Agent, request) remains compatible.
this is low risk, because it's only used in a test.
Changelog: [Internal]
Reviewed By: robhogan
Differential Revision: D93298172
fbshipit-source-id: be623702ebec1bd494c862f9c7990580f6b3cc4d
Summary:
Pull Request resolved: https://github.com/facebook/react-native/pull/55543
@public
This diff updates several Babel packages to their latest versions:
- `babel/code-frame`: 7.29.0
- `babel/generator`: 7.29.1
- `babel/parser`: 7.29.0
- `babel/template`: 7.28.6
- `babel/traverse`: 7.29.0
- `babel/types`: 7.29.0
Not bumping `core` or `runtime` here because they're a bit more involved, and I'm mainly interested in `traverse`. The packages here are the closure of traverse's dependency graph.
Changelog: [Internal]
Reviewed By: yungsters
Differential Revision: D92983519
fbshipit-source-id: 9f2e71fb5d453606c697d52539f0056b7a29bc45
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