Christian Falch
fd1e57b0c0
Summary: In the final XCFramework we no longer need to place resource bundles in a subfolder called Resources - they should be located directly in the framework folder. This commit fixes this by removing copying to the Resources folder. I also removed a few unneeded tests since we know that we are in a valid folder at this point. bypass-github-export-checks ## Changelog: [INTERNAL] - Moved resource bundles up one level Pull Request resolved: https://github.com/facebook/react-native/pull/50101 Test Plan: Run RNTester with RCT_USE_RN_DEP=1 and verify that it launches Reviewed By: cortinico Differential Revision: D71464608 Pulled By: cipolleschi fbshipit-source-id: 6cfdda0c6785ffeb13c170f9fd2dd9f5b889d490
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.