React Release Manager #7330
Merged
React Release Manager #7330
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
zpao
commented
Sep 27, 2016
| @@ -7,6 +7,7 @@ | |||
| "dependencies": { | |||
| "chalk": "^1.1.3", | |||
| "colors": "^1.1.2", | |||
| "es6-promisify": "^4.1.0", | |||
There was a problem hiding this comment.
We can revert this and just remove the dead require I added. I bet that's why lint is unhappy too…
Merged
This will publish all packages in build/packages/*.tgz to the "next" tag. If the current version is "stable" (doesn't trigger semver.prerelease()) then it will also update the "latest" dist-tag to point at that version.
This does the essentials for starting a new release on the stable branch
Now with - better UX (can skip, handle each failed cherr-pick individually) - easier to read code - better error handling / cancellation
gaearon
force-pushed
the
release-manager
branch
from
c986b10
to
27da779
Compare
This reverts commit c8cd133. It's not used in the code.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
❗️Not ready to be merged into
master, still a work in progress❗️Introducing the React Release Manager, built to replace all of the manual steps involved in maintaining & shipping React.
Primary focus so far has been the most time-intensive & error prone steps. But automating more of this process is super important as we want to be able to turn around releases much more quickly, and ensure more people feel confident doing it (I've run almost every release since we started)
Quick overview:
docs-prs: replaces a GH label search, opening a bunch of tabs, copying the merge sha, cherry-pick each of those, push, batch remove label on GHstable-prs: similar docs process but with milestonesversion: replaces manually editing a bunch of files before release (or other similar steps, eventually became me usingpatch)npm-publish: replaces a couple commands in my shell history, or a fancyls build/packages/*.tgz | xargs -n1 npm publishPlans:
publish: do the whole thingversion-start: create/update branches for release prep work (eg, just shipped 15.3.0, make sure dev branch exists)changelog: generate a naive version of the changelog from X to Y (maybe just added tostable-prscommand)