Skip to content

chore(deps): update testing-library monorepo - #1161

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/testing-library-monorepo
Open

chore(deps): update testing-library monorepo#1161
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/testing-library-monorepo

Conversation

@renovate

@renovate renovate Bot commented Aug 17, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
@testing-library/jest-dom 7.0.07.0.1 age confidence
@testing-library/user-event 14.6.314.6.4 age confidence

Release Notes

testing-library/jest-dom (@​testing-library/jest-dom)

v7.0.1

Compare Source

testing-library/user-event (@​testing-library/user-event)

v14.6.4

Compare Source


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • Monday through Friday (* * * * 1-5)
  • Automerge
    • At any time (no schedule defined)

🚦 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.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate Bot added the dependencies Pull requests that update a dependency file label Aug 17, 2026
@renovate
renovate Bot enabled auto-merge (squash) August 17, 2026 03:49
@renovate renovate Bot added the dependencies Pull requests that update a dependency file label Aug 17, 2026

@doistbot doistbot left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.json wasn't regenerated alongside the package.json bumps, so the two files are out of sync and npm ci will fail in CI. Run npm install (or npm install --package-lock-only) and commit the updated lockfile.

Share FeedbackReview Logs

Comment thread package.json
"@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",

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 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.

@renovate
renovate Bot force-pushed the renovate/testing-library-monorepo branch from 8753db3 to 803282c Compare August 17, 2026 17:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant