-
Notifications
You must be signed in to change notification settings - Fork 58
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
Update submodule dependencies #4383
Conversation
These changes originate from updated dependencies within the `gutenberg` submodule.
b12bad1
to
1afcc85
Compare
Wanna run full suite of Android and iOS UI tests? Click here and 'Approve' CI job! |
The outdated packages resulted in the following CI failure. ``` TypeError: snapshotResolver.resolveSnapshotPath is not a function at Object._default [as default] (node_modules/jest-jasmine2/build/setup_jest_globals.js:101:41) ``` These updates were completed to resolve the error and mirror updates within the `gutenberg` submodule, which updated `jest-snapshot`: WordPress/gutenberg#37396 The cause of the error is a breaking change that landed in `jest-snapshots@27`: jestjs/jest#8829
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.
I've just added a couple of minor comments, the PR LGTM 🎊 !
- Confirmed that CI checks are passing ✅
- Run
npm install
locally and verify thatpackage-lock.json
is not modified ✅
This reverts commit 6625413.
The Jest test runner found was resolving different version of Jest sub-dependencies, which resulted in the following error. ``` TypeError: snapshotResolver.resolveSnapshotPath is not a function at Object._default [as default] (node_modules/jest-jasmine2/build/setup_jest_globals.js:101:41) ``` Specifically, the test runner resolved `node_modules/[email protected] > gutenberg/node_modules/[email protected]`. `jest-snapshot@27` includes a breaking change of a newly returned `Promise`: jestjs/jest#8829 This reordering prioritizes the dependencies found in the top-level `node_modules` directory over the directory found within the `gutenberg` submodule.
This reverts commit 1afcc85.
These changes originate from updated dependencies within the `gutenberg` submodule. These changes are the result of clearing out all `node_modules` directories, and running `npm install` three times.
The proposed changes have changed drastically since review.
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.
The changes look good!
In the package-lock.json
file I see only changes to @types/react
and @types/react-dom
which come from the update to the Gutenberg submodule (I see the same version updates there).
Thanks so much @dcalhoun!
Update Gutenberg version and capture lock file changes originating from dependency updates within the
gutenberg
submodule.Additionally, the Jest test runner was resolving different version of Jest sub-dependencies, which resulted in the following error.
Specifically, the test runner resolved
node_modules/[email protected] > gutenberg/node_modules/[email protected]
.jest-snapshot@27
includes a breaking change of a newly returnedPromise
: jestjs/jest#8829This reordering prioritizes the dependencies found in the top-level
node_modules
directory over the directory found within thegutenberg
submodule. The origin of this incorrect module resolution is a combination of WordPress/gutenberg#37396 and WordPress/gutenberg#33448.To test: Passing CI checks should suffice.
PR submission checklist: