playground
playground copied to clipboard
chore(deps): update dependency @testing-library/react to v16
This PR contains the following updates:
Package | Change | Age | Adoption | Passing | Confidence |
---|---|---|---|---|---|
@testing-library/react | ^12.1.5 -> ^16.0.0 |
Release Notes
testing-library/react-testing-library (@testing-library/react)
v16.0.1
v16.0.0
Features
BREAKING CHANGES
-
@testing-library/dom
was moved to a peer dependency and needs to be explicitly installed. This reduces the chance of having conflicting versions of@testing-library/dom
installed that frequently caused bugs when used with@testing-library/user-event
. We will also be able to allow new versions of@testing-library/dom
being used without a SemVer major release of@testing-library/react
by just widening the peer dependency.@types/react-dom
needs to be installed if you're typechecking files using@testing-library/react
.
v15.0.7
v15.0.6
v15.0.5
v15.0.4
v15.0.3
Bug Fixes
v15.0.2
v15.0.1
v15.0.0
v14.3.1
Bug Fixes
v14.3.0
v14.2.2
v14.2.1
Bug Fixes
v14.2.0
Features
v14.1.2
Bug Fixes
v14.1.1
Bug Fixes
v14.1.0
Features
v14.0.0
Bug Fixes
Features
- Bump
@testing-library/dom
to 9.0.0 (#1177) (6653c23) - Drop support for Node.js 12.x (#1169) (9b7a1e2)
BREAKING CHANGES
- See https://github.com/testing-library/dom-testing-library/releases/tag/v9.0.0
- Minimum supported Node.js version is now 14.x
v13.4.0
Features
v13.3.0
Features
v13.2.0
Features
v13.1.1
Bug Fixes
v13.1.0
Features
v13.0.1
Bug Fixes
- Specify a non-* version for @types/react-dom (#1040) (2a889e8)
v13.0.0
Features
BREAKING CHANGES
- Drop support for React 17 and earlier. We'll use the new
createRoot
API by default which comes with a set of changes while also enabling support for concurrent features. To opt-out of this change you can userender(ui, { legacyRoot: true } )
. But be aware that the legacy root API is deprecated in React 18 and its usage will trigger console warnings.
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
- [ ] If you want to rebase/retry this PR, check this box
This PR was generated by Mend Renovate. View the repository job log.
⚠ Artifact update problem
Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.
♻ Renovate will retry this branch, including artifacts, only when one of the following happens:
- any of the package files in this branch needs updating, or
- the branch becomes conflicted, or
- you click the rebase/retry checkbox if found above, or
- you rename this PR's title to start with "rebase!" to trigger it manually
The artifact failure details are included below:
File name: package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/react
npm ERR! dev react@"^17.0.2" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer react@"^18.0.0" from @testing-library/[email protected]
npm ERR! node_modules/@testing-library/react
npm ERR! dev @testing-library/react@"^15.0.0" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR!
npm ERR! For a full report see:
npm ERR! /tmp/renovate/cache/others/npm/_logs/2024-04-22T01_05_51_456Z-eresolve-report.txt
npm ERR! A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-04-22T01_05_51_456Z-debug-0.log
⚠️ Artifact update problem
Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.
♻ Renovate will retry this branch, including artifacts, only when one of the following happens:
- any of the package files in this branch needs updating, or
- the branch becomes conflicted, or
- you click the rebase/retry checkbox if found above, or
- you rename this PR's title to start with "rebase!" to trigger it manually
The artifact failure details are included below:
File name: package-lock.json
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: [email protected]
npm error Found: [email protected]
npm error node_modules/react
npm error dev react@"^17.0.2" from the root project
npm error
npm error Could not resolve dependency:
npm error peer react@"^18.0.0" from @testing-library/[email protected]
npm error node_modules/@testing-library/react
npm error dev @testing-library/react@"^16.0.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2024-06-30T05_24_15_273Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-06-30T05_24_15_273Z-debug-0.log