[RN][Releases] Automate the check for the Release on NPM#49164
[RN][Releases] Automate the check for the Release on NPM#49164cipolleschi wants to merge 1 commit intomainfrom
Conversation
|
@cipolleschi has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator. |
6f7b6de to
1ad9ee1
Compare
|
@cipolleschi has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator. |
939717c to
9b19adc
Compare
|
@cipolleschi has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator. |
9b19adc to
afef98c
Compare
|
@cipolleschi has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator. |
afef98c to
05a9c02
Compare
|
@cipolleschi has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator. |
05a9c02 to
ac74d0c
Compare
|
@cipolleschi has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator. |
|
@cipolleschi merged this pull request in a52f551. |
|
This pull request was successfully merged by @cipolleschi in a52f551 When will my fix make it into a release? | How to file a pick request? |
Summary: These snuck in, presumably accidentally, via #49164. This interferes with running test suites with a debugger connected (e.g, when debugging Jest itself). (Aside: we should probably enable [`eslint/no-debugger`](https://eslint.org/docs/latest/rules/no-debugger) to catch these) Changelog: [Internal] Differential Revision: D69377992
Summary: Pull Request resolved: #49289 These snuck in, presumably accidentally, via #49164. This interferes with running test suites with a debugger connected (e.g, when debugging Jest itself). (Aside: we should probably enable [`eslint/no-debugger`](https://eslint.org/docs/latest/rules/no-debugger) to catch these) Changelog: [Internal] Reviewed By: hoxyq Differential Revision: D69377992 fbshipit-source-id: 5d51d18be76f9b01852b2e5b7297b95452f36d55
Summary:
One of the steps we perform when doing a release is to run
npm view react-nativeto verify that the release has been published and it is available with the right tag.As of today, we check this manually.
This change aims at automating this check so that we don't have to do it manually ourselves.
Changelog:
[Internal] - Releases: automate the npm view check
Test Plan:
Created a veriftyReleaseOnNPM-tests.js jest test to verify that the script works fine.