2 Commits

Author	SHA1	Message	Date
Riccardo Cipolleschi	90d4d55122	Port Create Release fixes from Stable to main (#45063) ... Summary: Pull Request resolved: https://github.com/facebook/react-native/pull/45063 While doing the release of 0.75, we have to fix the Create Release action a few times to get it right. This change contains the fixes from * https://github.com/facebook/react-native/commit/e36b46f0c970dc3f1f5b5058a8d10834acdb2667 * https://github.com/facebook/react-native/commit/1b891357b2f1995f2344cc991be423ca66fa6770 * https://github.com/facebook/react-native/commit/56e1c8bfdd57600e79c0b17de1d2fd933d20b8f9 * https://github.com/facebook/react-native/commit/03591318fbabdc0c06808316f471cc361b53c57f * https://github.com/facebook/react-native/commit/528097709aeef434b0d85565bfd89a4a9ff5644e * https://github.com/facebook/react-native/commit/f4b1dd1fa11374cae8a696833ad9ded0767cba8f ## Changelog [Internal] - Backport changes to Create Release github action Reviewed By: cortinico Differential Revision: D58782391 fbshipit-source-id: b68088fb8c4290efcb4599d1b090b18e401e4b66	2024-06-20 03:24:29 -07:00
Riccardo Cipolleschi	ece68f0efd	Remove the trigger-react-native-release to use the GHA workflow_dispatch UI (#44898) ... Summary: This change removes the need for the trigger-react-native-release.js script. Thanks to the migration to Github Actions, we can now leverage the GHA workflow UI to trigger a Prepare Release job that creates a github tag that will spin a new release. The pro of this approach are: - less code to maintain: instead of a complex trigger release scripts, we only have to maintain two very straightforward scripts for the CI - easier to trigger a release: instead of running a script, we can now just use the GH UI The `trigger-react-native-release` script was doing the following steps: - check that we are in the release branch ==> Already implemented in the GHA workflow - Gets the branch name (not needed) ==> the job will automatically run on the stable branch - Check for unsent changes (not needed) ==> we are not in a local environment - get the gh token (not needed) ==> You need to be logged in GH and have write access to the repo - get the version ==> provided as a parameter - fails if the tag is already there ==> Functionality added in the workflow - Parse and validate the version ==> Functionality added to the action prepare-release action + the JS Script - Compute the npmTag ==> Functionality added to the action prepare-release action + the JS Script - trigger the release workflow ==> The GH UI does that for us ## Changelog: [Internal] - Remove the trigger-react-native-release.js Pull Request resolved: https://github.com/facebook/react-native/pull/44898 Test Plan: Testing in Production! Reviewed By: cortinico, huntie Differential Revision: D58461470 Pulled By: cipolleschi fbshipit-source-id: 32bb0ee91370c9483a29e2ca2e18e24557d5fd53	2024-06-13 08:19:58 -07:00