Riccardo Cipolleschi
a6ea626255
Summary: Pull Request resolved: https://github.com/facebook/react-native/pull/51946 This change simplified the setp disallowing to use JSC from core. As a side effect, it simplified the setup by always falling back to hermes if the users decides not to use the third party JSC ## Changelog: [iOS][Removed] - remove the option to use JSC from core Reviewed By: cortinico Differential Revision: D76342625 fbshipit-source-id: c925ab4fab1e171e289a1c5f75890c92da1b3f08
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.