Christian Falch
e876e4926f
Summary: Pull Request resolved: https://github.com/facebook/react-native/pull/49969 Improved RCT-Folly podspec by configuring it as a prepare step, so that we don't need to forward the folly flags to all the others pods and to 3rd party dependencies. ## Changelog: [INTERNAL] - Configure folly in a prepare step Test Plan: ✅ Run Rn-Tester and verify that it works as expected both building deps from source and using prebuilt tarballs ✅ Add third-party library (react-native-reanimated) and perform the same tests to verify that it works with the changed podspec and utilities Reviewed By: javache Differential Revision: D71032640 Pulled By: cipolleschi fbshipit-source-id: a34a9b38fa5d5b37a0a193a73659f0d45dd3d660
scripts/releases
Scripts related to creating a React Native release. These are the lower level entry points used by scripts/releases-ci.
Commands
For information on command arguments, run node <command> --help.
create-release-commit
Creates a release commit to trigger a new release.
set-version
Bump the version of all packages.
- Updates
package.jsonmetadata for all workspaces and the project root. - Updates relevant native files in the
react-nativepackage.
If --skipReactNativeVersion is passed, the react-native package version will be left unmodified as "1000.0.0" (special static version on main), and native files will not be touched.
set-rn-artifacts-version
Note
Deprecated: Prefer
set-version. This entry point is a subset ofset-version, and is used only by test workflows. We will replace these call sites in future.
Updates relevant native files in the react-native package to materialize the given release version. This is run by set-version unless --skipReactNativeVersion is passed.