-
Notifications
You must be signed in to change notification settings - Fork 46.4k
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
Release checklist for 16 RC #10623
Labels
Comments
flarnie
added a commit
to flarnie/react
that referenced
this issue
Sep 6, 2017
**what is the change?:** Updates to the latest allowed versions for two dependencies. `yarn upgrade 'fbjs@^0.8.9'` and `yarn upgrade 'prop-types@^15.5.8'` **why make this change?:** Prepping for the 16.0 RC, we want to have a reproducible build that is as close as possible to what new users will get when installing React. **test plan:** `yarn && yarn build && yarn test` **issue:** facebook#10623
flarnie
added a commit
that referenced
this issue
Sep 6, 2017
**what is the change?:** Updates to the latest allowed versions for two dependencies. `yarn upgrade 'fbjs@^0.8.9'` and `yarn upgrade 'prop-types@^15.5.8'` **why make this change?:** Prepping for the 16.0 RC, we want to have a reproducible build that is as close as possible to what new users will get when installing React. **test plan:** `yarn && yarn build && yarn test` **issue:** #10623
flarnie
added a commit
to flarnie/react
that referenced
this issue
Sep 6, 2017
**what is the change?:** See title **why make this change?:** We want the `art` fixture to be working so that we can test the latest version of `react-art`. **test plan:** Built and inspected the fixture manually **issue:** Prepping for 16.0RC release - facebook#10623
flarnie
added a commit
that referenced
this issue
Sep 6, 2017
* Add missing dependencies in `art` fixture, update `yarn.lock` **what is the change?:** See title **why make this change?:** We want the `art` fixture to be working so that we can test the latest version of `react-art`. **test plan:** Built and inspected the fixture manually **issue:** Prepping for 16.0RC release - #10623 * ran prettier
🎉 w00t~ |
flarnie
added a commit
to flarnie/react
that referenced
this issue
Sep 8, 2017
…k#10626) **what is the change?:** Updates to the latest allowed versions for two dependencies. `yarn upgrade 'fbjs@^0.8.9'` and `yarn upgrade 'prop-types@^15.5.8'` **why make this change?:** Prepping for the 16.0 RC, we want to have a reproducible build that is as close as possible to what new users will get when installing React. **test plan:** `yarn && yarn build && yarn test` **issue:** facebook#10623
flarnie
added a commit
to flarnie/react
that referenced
this issue
Sep 8, 2017
…ok#10628) * Add missing dependencies in `art` fixture, update `yarn.lock` **what is the change?:** See title **why make this change?:** We want the `art` fixture to be working so that we can test the latest version of `react-art`. **test plan:** Built and inspected the fixture manually **issue:** Prepping for 16.0RC release - facebook#10623 * ran prettier
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Ensure all commits in master were tested at Facebook.
Verify that you have npm permissions.
npm owner ls react
npm owner ls react-art
npm owner ls react-dom
npm owner ls react-test-renderer
Ensure your React is fresh.
master
git pull
git log
output matches the commit list.yarn
in the repo root.Ensure runtime dependencies match what users would get.
For
fbjs
:fbjs
in rootpackage.json
.packages/*/package.json
depending onfbjs
specify the same range.yarn upgrade fbjs@^THAT_VERSION
in the repo root. (Don’t miss the caret!)For
object-assign
:object-assign
in rootpackage.json
.packages/*/package.json
depending onobject-assign
specify the same range.yarn upgrade object-assign@^THAT_VERSION
in the repo root. (Don’t miss the caret!)For
prop-types
:prop-types
in rootpackage.json
.packages/*/package.json
depending onprop-types
specify the same range.yarn upgrade prop-types@^THAT_VERSION
in the repo root. (Don’t miss the caret!)This might change the lockfile. This should not change any
package.json
.Commit the changes, if any. (see Update to latest allowed versions of
fbjs
andprop-types
#10626)Edit:
react-art
is broken in the 16 branch but this shouldn't block RC, and will be fixed asap by @sophiebits and @flarnie in Pull in react-art/lib/{Circle,Rectangle,Wedge}.art #10629Do the local sanity checks in the repo root.
yarn test
in the repo root.yarn lint
in the repo root.yarn flow
in the repo root.STABLE RELEASE ONLY: Update error codes.
yarn build -- --extract-errors
in the repo root.scripts/error-codes/codes.json
changes,git commit -am 'Update error codes'
*-stable
branch for docs when you’re reading this, we need to cherry-pick that commit to that branch. This makes sure the website decoder knows about the updated error codes. But ideally we should just change docs to serve from master.(See #10619 #10621 and #10622)
Update the version.
src/ReactVersion.js
version
in allpackages/*/package.json
:packages/react-art/package.json
packages/react-dom/package.json
packages/react-noop-renderer/package.json
packages/react-test-renderer/package.json
yarn version-check
to verify your changes.git commit -am "<version number>"
Build it!
yarn build
in the repo root.Run fast packaging smoke test.
fixtures/packaging/babel-standalone/dev.html
in the browser for a smoke test.Run slow packaging smoke test.
cd fixtures/packaging
and runnode build-all.js
npm install -g serve
serve -s .
Release!
git push
git push --tags
build/packages
npm publish --tag next
in the subfolder.npm publish
in the subfolder.Bonus: Try it out!
create-react-app myapp
cd myapp
npm start
The text was updated successfully, but these errors were encountered: