chore(deps): update testing-library monorepo - #1161
Conversation
doistbot
left a comment
There was a problem hiding this comment.
Routine patch bumps to @testing-library/jest-dom (7.0.0 → 7.0.1) and @testing-library/user-event (14.6.3 → 14.6.4), both dev-only dependencies with no source changes.
Few things worth tightening:
package-lock.jsonwasn't regenerated alongside thepackage.jsonbumps, so the two files are out of sync andnpm ciwill fail in CI. Runnpm install(ornpm install --package-lock-only) and commit the updated lockfile.
| "@storybook/react-vite": "10.5.7", | ||
| "@testing-library/dom": "10.4.1", | ||
| "@testing-library/jest-dom": "7.0.0", | ||
| "@testing-library/jest-dom": "7.0.1", |
There was a problem hiding this comment.
package.json now pins @testing-library/jest-dom at 7.0.1 and @testing-library/user-event at 14.6.4, but package-lock.json still records the old versions (7.0.0 at the root packages[""].devDependencies entry and node_modules/@testing-library/jest-dom, and 14.6.3 for node_modules/@testing-library/user-event). npm ci requires the manifest and lockfile to be in sync, so the CI jobs that run npm ci (e.g. check-ci-validation.yml, chromatic.yml, publish-package-release.yml) will fail on this branch. Regenerate the lockfile with npm install (or npm install --package-lock-only) and commit the updated package-lock.json.
8753db3 to
803282c
Compare
This PR contains the following updates:
7.0.0→7.0.114.6.3→14.6.4Release Notes
testing-library/jest-dom (@testing-library/jest-dom)
v7.0.1Compare Source
testing-library/user-event (@testing-library/user-event)
v14.6.4Compare Source
Configuration
📅 Schedule: (UTC)
* * * * 1-5)🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.