diff --git a/website/contributing/_markdown-older-bump-script.mdx b/website/contributing/_markdown-older-bump-script.mdx new file mode 100644 index 00000000000..f3aa2130b8c --- /dev/null +++ b/website/contributing/_markdown-older-bump-script.mdx @@ -0,0 +1,3 @@ +:::info +For versions older than 0.70, you need to run `./scripts/bump-oss-version.js` instead. +::: diff --git a/website/contributing/release-branch-cut-and-rc0.md b/website/contributing/release-branch-cut-and-rc0.md index c2f2fbb2d60..470b05e855f 100644 --- a/website/contributing/release-branch-cut-and-rc0.md +++ b/website/contributing/release-branch-cut-and-rc0.md @@ -4,6 +4,7 @@ title: Branch Cut & RC0 --- import AsyncTestingNote from './\_markdown-async-testing-note.mdx'; +import BumpOSSNote from './\_markdown-older-bump-script.mdx'; import GHReleasesNotesPrerelease from './\_markdown-GH-release-notes-prerelease.mdx'; import RoadToReleaseTemplate from './\_markdown-road-to-release-template.mdx'; @@ -63,11 +64,13 @@ Before continuing further, follow the [testing guide](/contributing/release-test Once you're done with the testing, you can kick-off the bump and publishing of RC0: -``` +```bash # This will walk you through what version you are releasing -./scripts/bump-oss-version.js --to-version 0.69.0-rc.0 --token +yarn trigger-react-native-release --to-version 0.69.0-rc.0 --token ``` + + - Once you have run that script, head to CircleCI and you should see under the releases workflow, a `prepare-package-for-release` job.
diff --git a/website/contributing/release-candidate-patch.md b/website/contributing/release-candidate-patch.md index 7fb67095201..88a82a53312 100644 --- a/website/contributing/release-candidate-patch.md +++ b/website/contributing/release-candidate-patch.md @@ -5,6 +5,7 @@ title: RC Patches import AsyncTestingNote from './\_markdown-async-testing-note.mdx'; import GHReleasesNotesPrerelease from './\_markdown-GH-release-notes-prerelease.mdx'; +import BumpOSSNote from './\_markdown-older-bump-script.mdx'; :::info Documents in this section go over steps to run different types of React Native release updates. Its intended audience is those in [relevant release roles](./release-roles-responsibilites.md). @@ -46,7 +47,7 @@ Before continuing further, follow the [testing guide](/contributing/release-test -### 4. Run `bump-oss-version` script +### 4. Run `trigger-react-native-release` script ```bash # once verified all the cherry-picked commits, we can push them to remote @@ -54,9 +55,11 @@ git push # run a script to bump the version # You **do not** want this release marked as "latest"! -./scripts/bump-oss-version.js --to-version 0.y.0-rc.x --token +yarn trigger-react-native-release --to-version 0.y.0-rc.x --token ``` + + ### 5. Watch CircleCI to ensure right jobs are being triggered - Once you have run the bump script script, head to CircleCI and you should see under the releases workflow, a `prepare-package-for-release` job. diff --git a/website/contributing/release-stable-minor.md b/website/contributing/release-stable-minor.md index 496a749c18e..cf83dce1dc3 100644 --- a/website/contributing/release-stable-minor.md +++ b/website/contributing/release-stable-minor.md @@ -3,6 +3,8 @@ id: release-stable-minor title: Minor Stable 0.Y.0 --- +import BumpOSSNote from './\_markdown-older-bump-script.mdx'; + :::info Documents in this section go over steps to run different types of React Native release updates. Its intended audience is those in [relevant release roles](./release-roles-responsibilites.md). ::: @@ -23,12 +25,14 @@ Documents in this section go over steps to run different types of React Native r # Make sure you are on the release branch of the version git checkout -b 0.Y-stable -./scripts/bump-oss-version.js --to-version 0.Y.0 --token +yarn trigger-react-native-release --to-version 0.Y.0 --token > Do you want this to be latest? # Reply to this prompt with "yes". # This updates npm registry to point to this version as "latest" ``` + + When this is done, all the other PRs (changelog, documentation, blog post) should also get merged. ### 2. Update the GitHub releases diff --git a/website/contributing/release-stable-patch.md b/website/contributing/release-stable-patch.md index 02f5dda55e7..c599aa19767 100644 --- a/website/contributing/release-stable-patch.md +++ b/website/contributing/release-stable-patch.md @@ -4,6 +4,7 @@ title: Minor Stable Patches --- import AsyncTestingNote from './\_markdown-async-testing-note.mdx'; +import BumpOSSNote from './\_markdown-older-bump-script.mdx'; :::info Documents in this section go over steps to run different types of React Native release updates. Its intended audience is those in [relevant release roles](./release-roles-responsibilites.md). @@ -62,7 +63,7 @@ Before continuing further, follow the [testing guide](/contributing/release-test -### 4. Run `bump-oss-version` script +### 4. Run `trigger-react-native-release` script ```bash # once verified all the cherry-picked commits, we can push them to remote @@ -70,9 +71,11 @@ git push # run a script to bump the version # If you are doing this patch release for the current latest minor, then mark it as "latest" -./scripts/bump-oss-version.js --to-version x.y.z --token +yarn trigger-react-native-release --to-version x.y.z --token ``` + + ### 5. Watch CircleCI to ensure right jobs are being triggered - Once you have run the bump script script, head to CircleCI and you should see under the releases workflow, a `prepare-package-for-release` job.