chore(deps): update testing-library monorepo (major) #1063
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
Branch automerge failureThis PR was configured for branch automerge. However, this is not possible, so it has been raised as a PR instead.
|
renovate
bot
force-pushed
the
renovate/major-testing-library-monorepo
branch
9 times, most recently
from
4e3a84e to
0fdec1e
Compare
renovate
bot
force-pushed
the
renovate/major-testing-library-monorepo
branch
7 times, most recently
from
e25da57 to
b62ce2a
Compare
renovate
bot
force-pushed
the
renovate/major-testing-library-monorepo
branch
3 times, most recently
from
99edf4e to
a6465c7
Compare
renovate
bot
force-pushed
the
renovate/major-testing-library-monorepo
branch
from
a6465c7 to
de872d7
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
5.17.0->6.6.312.1.5->16.1.0Release Notes
testing-library/jest-dom (@testing-library/jest-dom)
v6.6.3Compare Source
v6.6.2Compare Source
Bug Fixes
v6.6.1Compare Source
v6.6.0Compare Source
v6.5.0Compare Source
v6.4.8Compare Source
v6.4.7Compare Source
v6.4.6Compare Source
Bug Fixes
v6.4.5Compare Source
Bug Fixes
v6.4.4Compare Source
v6.4.3Compare Source
v6.4.2Compare Source
Bug Fixes
v6.4.1Compare Source
Bug Fixes
TestingLibraryMatchersfrom "./matchers" (#576) (dd1c4dd)v6.4.0Compare Source
Features
v6.3.0Compare Source
Features
v6.2.1Compare Source
Bug Fixes
v6.2.0Compare Source
Features
v6.1.6Compare Source
Bug Fixes
v6.1.5Compare Source
Bug Fixes
v6.1.4Compare Source
Bug Fixes
@adobe/css-toolsto4.3.1to address vulnerability (#532) (44f1eab)v6.1.3Compare Source
Bug Fixes
v6.1.2Compare Source
Bug Fixes
v6.1.1Compare Source
Bug Fixes
v6.1.0Compare Source
Features
v6.0.1Compare Source
Bug Fixes
v6.0.0Compare Source
Features
BREAKING CHANGES
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:
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'
testing-library/react-testing-library (@testing-library/react)
v16.1.0Compare Source
v16.0.1Compare Source
v16.0.0Compare Source
Features
@testing-library/domand@types/react-domto peer dependencies (#1305) (a4744fa)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.7Compare Source
v15.0.6Compare Source
v15.0.5Compare Source
v15.0.4Compare Source
v15.0.3Compare Source
Bug Fixes
document(#1304) (067d0c6)v15.0.2Compare Source
v15.0.1Compare Source
v15.0.0Compare Source
v14.3.1Compare Source
Bug Fixes
v14.3.0Compare Source
v14.2.2Compare Source
v14.2.1Compare Source
Bug Fixes
v14.2.0Compare Source
Features
reactStrictModeoption to enable strict mode render (#1241) (0880eba)v14.1.2Compare Source
Bug Fixes
v14.1.1Compare Source
Bug Fixes
v14.1.0Compare Source
Features
v14.0.0Compare Source
Bug Fixes
Features
@testing-library/domto 9.0.0 (#1177) (6653c23)BREAKING CHANGES
v13.4.0Compare Source
Features
v13.3.0Compare Source
Features
globalThisif available (#1070) (c80809a)v13.2.0Compare Source
Features
v13.1.1Compare Source
Bug Fixes
v13.1.0Compare Source
Features
renderHook(#991) (9535eff)v13.0.1Compare Source
Bug Fixes
v13.0.0Compare Source
Features
BREAKING CHANGES
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 use
render(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.
This PR was generated by Mend Renovate. View the repository job log.