-
Notifications
You must be signed in to change notification settings - Fork 46.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Publish a local release (canary or stable) to NPM #14260
Publish a local release (canary or stable) to NPM #14260
Conversation
26001f6
to
8f6e199
Compare
My last commit was totally unnecessary, but I thought I might as well replace our scattered These colors look best on a dark terminal themes, but I think they are also legible with a white terminal background. The yellow and green text are a little bit low contrast with light themes, but...it's probably okay? |
Also updated Circle CI build script to generate and add a build-info.json file to artifacts
5ff1d68
to
26a00aa
Compare
Rebased and added a new artifact to the Circle CI config– the error codes JSON. Going to let CI run to see if I configured it correctly. If so, I'm going to try to use this artifact when promoting a canary to stable so that I can avoid re-building it. |
This commit also temporarily changes an error message so I can verify the updated error codes JSON
console.log( | ||
theme`A full diff is availbale at {path ${relative(cwd, diffPath)}}.` | ||
); | ||
await confirm('Do changes changes look correct?'); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Typo?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Typo on "availbale" in line 161 too
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Whoops, yes.
8ba1f03
to
3585929
Compare
During our chat today, Sunil, it occurred to me that I could pretty easily auto-stage changes to package JSONs after a stable publish by just copying over portions of the just-published package JSON (40dde41). |
4b99ae2
to
03182f4
Compare
03182f4
to
40dde41
Compare
🕺 |
Top right of the page should have options to approve/request changes/comment. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
tested/verified dry runs
New release scripts. Learn more at https://github.com/facebook/react/blob/master/scripts/release/README.md
Issue #14201. Builds on top of #14255 (view the delta).
This PR adds the final
publish
script and does a bit of cleanup of the pre-existing scripts. (For example, thebuild
script is no longer needed and so it has been removed.)This PR also removes the pre-build "version-check" behavior since there is an expected version mismatch between canary packages and the embedded React version (used by DevTools). If this change is controversial, I'm happy to elaborate on why I chose this detail and discuss alternatives.
Learn more about these new release scripts here.
Demos
Checking out a Circle CI build for a canary release
Preparing a canary release to be promoted to stable
Publishing a release
Resuming an interrupted publish (dry run)
Creating a local canary (escape hatch)
Note that I trimmed the middle out of this GIF since building takes a long time.