mirror of
https://github.com/facebook/react-native.git
synced 2025-11-01 09:14:26 +00:00
Nicola Corti
1c5e0ffd9f
Summary: Pull Request resolved: https://github.com/facebook/react-native/pull/53817 What is currently happening, is that the various commits on the release branches like `0.82-stable` are resetting the version of native artifacts to `1000.0.0-<SHA>`. The reason is that during the `test-all` workflow, we pass the `dry-run` as release type. That's to prevent the various tools from calling `npm publish` and so on. The problem is that on the releases branches, the version was already set at branch cut time. Therefore, we see the version 1000.0.0 reappearing during Android E2E test in the emulator. Similary this is also affecting iOS prebuilds so I'm attempting to fix it here. Changelog: [Internal] [Changed] - Reviewed By: huntie Differential Revision: D82553599 fbshipit-source-id: 31a52e7df036e700663b3d3dd677973a7a210a30
scripts/releases-ci
CI-only release scripts — intended to run from a CI workflow (GitHub Actions).
Commands
For information on command arguments, run node <command> --help.
prepare-package-for-release
Prepares files within the react-native package and template for the target release version. Writes a new commit and tag, which will trigger publish-npm.js in a new workflow.
publish-npm
Prepares release artifacts and publishes the react-native package to npm.
publish-updated-packages
Publishes all updated packages (excluding react-native) to npm. Triggered when a commit on a release branch contains #publish-packages-to-npm.