mirror of
https://github.com/facebook/react-native.git
synced 2025-11-01 09:14:26 +00:00
Luna Wei
76a2cf3569
Summary: Changelog: [Internal] * Refactor release automation so it doesn't use intermediate tags to trigger the release workflow. Now, we POST to CircleCI's ["trigger pipeline" API](https://circleci.com/docs/api/v2/#operation/triggerPipeline) * This does have the con of needing to give CircleCI project permission for whoever wants to run a release as you'll need a token to trigger * See related discussion: https://github.com/reactwg/react-native-releases/discussions/7#discussioncomment-1836420 Description of changes: * Changes to config.yml allow us to use our POST data to trigger a certain workflow. There is no direct API to trigger a workflow, CircleCI only has an API to trigger pipelines, so the suggestion is to leverage conditionals: https://support.circleci.com/hc/en-us/articles/360050351292-How-to-trigger-a-workflow-via-CircleCI-API-v2 * Update `bump-oss-version` to make the api call -- the instructions for running a release are still the same: https://github.com/facebook/react-native/wiki/Release-Process#creating-0minor0-rc0 * Would be good to make this a yarn script as tido64 mentioned * Remove unused utilities now that we don't use intermediate tags like `publish-...` Pull Request resolved: https://github.com/facebook/react-native/pull/32937 Test Plan: Have this on a Github branch and tried this out locally: ## Running release script Running the bump-oss script (I had to hack it locally to be allowed to run on a non-release branch): {F694804729} * Link to resulting workflow: https://app.circleci.com/pipelines/github/facebook/react-native/11836 -- you can [verify that the parameters are the same as I passed](https://app.circleci.com/pipelines/github/facebook/react-native/11836/workflows/59ac0c86-5fe3-4d7a-80e9-c61129d49e9f/jobs/232388?invite=true#step-106-2) ## Other attempts triggering this workflow Notice that when I tried to run it on an actual release-branch (0.67-stable) but because the `config.yml` changes aren't on that branch, the job faisl | {F694804321} | ## Verifying the right workflows trigger on a regular push * Notice that the workflows "analysis" and "test" are still triggered on push (ie, the `unless:` clause isn't messing things up) {F694804320} Reviewed By: sota000 Differential Revision: D33715336 Pulled By: lunaleaps fbshipit-source-id: 82672d6d50768015bdfc9f4ea4d22aa801b84f06
99 lines
2.7 KiB
JavaScript
Executable File
99 lines
2.7 KiB
JavaScript
Executable File
/**
|
|
* Copyright (c) Meta Platforms, Inc. and affiliates.
|
|
*
|
|
* This source code is licensed under the MIT license found in the
|
|
* LICENSE file in the root directory of this source tree.
|
|
*
|
|
* @format
|
|
*/
|
|
|
|
'use strict';
|
|
|
|
/**
|
|
* This script prepares a release package to be pushed to npm
|
|
* It is triggered to run on CircleCI
|
|
* It will:
|
|
* * It updates the version in json/gradle files and makes sure they are consistent between each other (set-rn-version)
|
|
* * Updates podfile for RNTester
|
|
* * Commits changes and tags with the next version based off of last version tag.
|
|
* This in turn will trigger another CircleCI job to publish to npm
|
|
*/
|
|
const {echo, exec, exit} = require('shelljs');
|
|
const yargs = require('yargs');
|
|
const {isReleaseBranch, parseVersion} = require('./version-utils');
|
|
|
|
const argv = yargs
|
|
.option('r', {
|
|
alias: 'remote',
|
|
default: 'origin',
|
|
})
|
|
.option('v', {
|
|
alias: 'to-version',
|
|
type: 'string',
|
|
required: true,
|
|
})
|
|
.option('l', {
|
|
alias: 'latest',
|
|
type: 'boolean',
|
|
default: false,
|
|
}).argv;
|
|
|
|
const currentCommit = process.env.CIRCLE_SHA1;
|
|
const branch = process.env.CIRCLE_BRANCH;
|
|
const remote = argv.remote;
|
|
const releaseVersion = argv.toVersion;
|
|
const isLatest = argv.latest;
|
|
|
|
if (!isReleaseBranch(branch)) {
|
|
console.error(`This needs to be on a release branch. On branch: ${branch}`);
|
|
exit(1);
|
|
}
|
|
|
|
const {version} = parseVersion(releaseVersion);
|
|
if (version == null) {
|
|
console.error(`Invalid version provided: ${releaseVersion}`);
|
|
exit(1);
|
|
}
|
|
|
|
if (exec(`node scripts/set-rn-version.js --to-version ${version}`).code) {
|
|
echo(`Failed to set React Native version to ${version}`);
|
|
exit(1);
|
|
}
|
|
|
|
// Release builds should commit the version bumps, and create tags.
|
|
echo('Updating RNTester Podfile.lock...');
|
|
if (exec('source scripts/update_podfile_lock.sh && update_pods').code) {
|
|
echo('Failed to update RNTester Podfile.lock.');
|
|
echo('Fix the issue, revert and try again.');
|
|
exit(1);
|
|
}
|
|
|
|
// Make commit [0.21.0-rc] Bump version numbers
|
|
if (exec(`git commit -a -m "[${version}] Bump version numbers"`).code) {
|
|
echo('failed to commit');
|
|
exit(1);
|
|
}
|
|
|
|
// Add tag v0.21.0-rc.1
|
|
if (exec(`git tag -a v${version} -m "v${version}"`).code) {
|
|
echo(
|
|
`failed to tag the commit with v${version}, are you sure this release wasn't made earlier?`,
|
|
);
|
|
echo('You may want to rollback the last commit');
|
|
echo('git reset --hard HEAD~1');
|
|
exit(1);
|
|
}
|
|
|
|
// If `isLatest`, this git tag will also set npm release as `latest`
|
|
if (isLatest) {
|
|
exec('git tag -d latest');
|
|
exec(`git push ${remote} :latest`);
|
|
|
|
// This will be pushed with the `--follow-tags`
|
|
exec('git tag -a latest -m "latest"');
|
|
}
|
|
|
|
exec(`git push ${remote} ${branch} --follow-tags`);
|
|
|
|
exit(0);
|