You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[0.87] Derive generated SPM manifests from shared name constants #1387
The SwiftPM pipeline currently repeats React Native internal package and product names across several manifest generators and scaffolders. That duplication allows the generated manifests and Xcode project references to drift, and prevents the pipeline from reliably guarding against user package names that collide with React Native built-in packages, as reported by the community in powersync-ja/powersync-js#1076.
This commit centralizes the internal SwiftPM package and product names in spm-utils.js, derives the generated manifests, autolinking dependencies, scaffolded packages, and Xcode project product references from those shared constants, and adds focused unit coverage. It is the prerequisite refactor for adding collision guards while keeping every generated SwiftPM artifact consistent.
The change does not alter the public package or product names. Validation on main includes the focused unit tests from react/react-native#58035.
Thank you for opening a new React Native Pick Request.
These are the criteria we follow when accepting or rejecting a code change into a React Native release branch (source).
If your Pick Request does not satisfy the criteria below, please close it as it will not be considered.
✅ Which Pick Requests we accept
✅ Fixes for regressions to core APIs. Examples:
A core component is behaving differently between versions 0.X and 0.X-1
The TurboModule.getEnforcing function is throwing an unexpected assertion error.
✅ Fixes to bugs in core React Native. Examples:
Breakpoints in React Native DevTools not working correctly in the debugger
Fast Refresh not working as expected
Metro bundler not starting properly or ignoring the configuration file
Buttons that are not clickable
✅ Fixes to APIs used by third-party libraries and out-of-tree platforms. Examples:
An API used by react-native-macos is not behaving as expected or is regressing
✅ Bump of patch version of dependencies. Example:
Bump Gradle from 8.11.0 to 8.11.1
✅ Fixes for low/high severity security vulnerabilities. Example:
Bump Gradle from 8.11.0 to 8.12.0 if there is a security vulnerability in 8.11 and no 8.11.x version contains the same fix.
✅ Fixes and reverts of accidental breaking changes. Example:
Reverting or fix-forwarding a Kotlin migration of a file (e.g. ReactRootView.java) if it is causing a breaking change for the React Native ecosystem.
✅ Performance improvements. Examples:
Fixing unnecessary re-renders in FlatList.
✅ Any Pick Request if the release is still in RC0 (after RC1, the previously listed criteria apply)
❌ Which Pick Requests we don't accept
❌ Any Pick Request that introduces a breaking change after RC1. Example:
A bugfix that contains a refactoring, resulting in changes to the public API of a class
❌ Any Pick Request that introduces a new feature after RC1. Example:
A commit that introduces a new API or a specific feature for a component.
❌ Bump of major or minor version of dependencies. Examples:
Bump Gradle from 8.11.0 to 8.12.0
Bump Gradle from 8.11.0 to 9.0.0
❌ Bump of a dependency to a pre-release version. Example:
Bump Gradle from 8.11.0 to 8.11.1-beta.1
❌ Any Pick Request that introduces changes to the React Native testing infrastructure after RC1. Examples:
Changes to GitHub Actions workflows to optimize them, even if they are on main.
Changes to the logic used to publish packages to NPM or Maven Central
❌ Pick Request composed of multiple commits that have several merge conflicts.
If your Pick Request is too complex to apply to the release branch, it will be rejected.
❌ Any non-critical improvement that landed on main.
These will generally ship in the following version unless they fit one of the criteria above.
❌ Any Pick Request considered a "nice to have".
Even one-line changes carry a risk of destabilizing and further delaying the release.
ℹ️ What makes for a good Pick Request
In order for your Pick Request to be considered, please do the following:
ℹ️ Limit your Pick Request to one commit from main, or one PR against the release branch.
ℹ️ Include a clear explanation of why your Pick Request should be considered, ideally referencing one of the criteria above.
ℹ️ Target only one minor version of React Native (e.g. [0.76]). To have your Pick Request applied to more versions, please open separate Pick Requests.
Activity
github-actions commentedon Aug 21, 2026
Thank you for opening a new React Native Pick Request.
These are the criteria we follow when accepting or rejecting a code change into a React Native release branch (source).
If your Pick Request does not satisfy the criteria below, please close it as it will not be considered.
✅ Which Pick Requests we accept
TurboModule.getEnforcingfunction is throwing an unexpected assertion error.react-native-macosis not behaving as expected or is regressingReactRootView.java) if it is causing a breaking change for the React Native ecosystem.❌ Which Pick Requests we don't accept
ℹ️ What makes for a good Pick Request
In order for your Pick Request to be considered, please do the following:
main, or one PR against the release branch.cipolleschi commentedon Aug 26, 2026
Included in for the 0.87.1 release via react/react-native@cdb180ce4f8e. Closing this pick request.
cipolleschi commentedon Aug 26, 2026
Correction: included in branch 0.87-stable for the 0.87.1 release. The commit link in the previous comment is correct.