polar
polar copied to clipboard
chore(deps): update testing-library monorepo (major)
This PR contains the following updates:
| Package | Change | Age | Adoption | Passing | Confidence |
|---|---|---|---|---|---|
| @testing-library/jest-dom | 5.17.0 -> 6.6.3 |
||||
| @testing-library/react | 12.1.5 -> 16.3.0 |
Release Notes
testing-library/jest-dom (@testing-library/jest-dom)
v6.6.3
Bug Fixes
v6.6.2
Bug Fixes
v6.6.1
Bug Fixes
v6.6.0
Features
v6.5.0
Features
v6.4.8
Bug Fixes
v6.4.7
Bug Fixes
v6.4.6
Bug Fixes
- Support @starting-style (#602) (fd9ee68)
v6.4.5
Bug Fixes
v6.4.4
Bug Fixes
v6.4.3
Bug Fixes
v6.4.2
Bug Fixes
- Remove errant export of GetByRoleMatcher, fixing type checking in some TS configurations (#575) (a93c0c4)
v6.4.1
Bug Fixes
v6.4.0
Features
v6.3.0
Features
v6.2.1
Bug Fixes
v6.2.0
Features
v6.1.6
Bug Fixes
- Upgrade @adobe/css-tools to v4.3.2 (#553) (b64b953)
v6.1.5
Bug Fixes
v6.1.4
Bug Fixes
v6.1.3
Bug Fixes
- proper @jest/globals import (#530) (5b492ac)
v6.1.2
Bug Fixes
- bump @adobe/css-tools for ESM support (#525) (b959a68)
v6.1.1
Bug Fixes
v6.1.0
Features
- Publish ESM and CJS (https://github.com/testing-library/jest-dom/pull/519)
v6.0.1
Bug Fixes
v6.0.0
Features
- local types, supporting jest, @jest/globals, vitest (#511) (4b764b9)
BREAKING CHANGES
- Removes the extend-expect script. Users should use the default import path or one of the new test platform-specific paths to automatically extend the appropriate "expect" instance.
extend-expect was not documented in the Readme, so this change should have minimal impact.
Users can now use the following import paths to automatically extend "expect" for their chosen test platform:
- @testing-library/jest-dom - jest (@types/jest)
- @testing-library/jest-dom/jest-globals - @jest/globals
- @testing-library/jest-dom/vitest - vitest
For example:
import '@testing-library/jest-dom/jest-globals'
Importing from one of the above paths will augment the appropriate matcher interface for the given test platform, assuming the import is done in a .ts file that is included in the user's tsconfig.json.
It's also (still) possible to import the matchers directly without side effects:
import * as matchers from '@testing-library/jest-dom/matchers'
- Update kcd-scripts
- Drop node < 14
testing-library/react-testing-library (@testing-library/react)
v16.3.0
v16.2.0
Features
v16.1.0
Features
v16.0.1
Bug Fixes
v16.0.0
Features
BREAKING CHANGES
@testing-library/domwas moved to a peer dependency and needs to be explicitly installed. This reduces the chance of having conflicting versions of@testing-library/dominstalled that frequently caused bugs when used with@testing-library/user-event. We will also be able to allow new versions of@testing-library/dombeing used without a SemVer major release of@testing-library/reactby just widening the peer dependency.@types/react-domneeds to be installed if you're typechecking files using@testing-library/react.
v15.0.7
Bug Fixes
v15.0.6
Bug Fixes
v15.0.5
Bug Fixes
v15.0.4
Bug Fixes
v15.0.3
Bug Fixes
v15.0.2
Bug Fixes
v15.0.1
Bug Fixes
v15.0.0
Release
BREAKING CHANGES
- Minimum supported Node.js version is 18.0
- New version of
@testing-library/domchanges various roles. Check out the changed tests in https://github.com/testing-library/dom-testing-library/commit/2c570553d8f31b008451398152a9bd30bce362b3 to get an overview about what changed.
v14.3.1
Bug Fixes
v14.3.0
Features
v14.2.2
Bug Fixes
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/domto 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
createRootAPI 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: 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.
Branch automerge failure
This PR was configured for branch automerge. However, this is not possible, so it has been raised as a PR instead.
- Branch has one or more failed status checks