Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(dev-deps): update testing-library monorepo (major) #231

Merged
merged 1 commit into from
Sep 16, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Sep 16, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@testing-library/jest-dom 5.17.0 -> 6.5.0 age adoption passing confidence
@testing-library/react 12.1.5 -> 16.0.1 age adoption passing confidence

Release Notes

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

v6.5.0

Compare Source

v6.4.8

Compare Source

v6.4.7

Compare Source

v6.4.6

Compare Source

Bug Fixes

v6.4.5

Compare Source

Bug Fixes

v6.4.4

Compare Source

v6.4.3

Compare Source

v6.4.2

Compare Source

Bug Fixes
  • Remove errant export of GetByRoleMatcher, fixing type checking in some TS configurations (#​575) (a93c0c4)

v6.4.1

Compare Source

Bug Fixes
  • Export type TestingLibraryMatchers from "./matchers" (#​576) (dd1c4dd)

v6.4.0

Compare Source

Features

v6.3.0

Compare Source

Features

v6.2.1

Compare Source

Bug Fixes
  • Standalone types for "./matchers" export and add Bun support (#​566) (5675b86)

v6.2.0

Compare Source

Features
  • toHaveAccessibleDescription supports aria-description (#​565) (1fb156c)

v6.1.6

Compare Source

Bug Fixes

v6.1.5

Compare Source

Bug Fixes

v6.1.4

Compare Source

Bug Fixes
  • upgrade @adobe/css-tools to 4.3.1 to address vulnerability (#​532) (44f1eab)

v6.1.3

Compare Source

Bug Fixes

v6.1.2

Compare Source

Bug Fixes

v6.1.1

Compare Source

Bug Fixes

v6.1.0

Compare Source

Features

v6.0.1

Compare Source

Bug Fixes
  • matchers type is making the global expect unsafe (#​513) (bdb34f1)

v6.0.0

Compare Source

Features
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:

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

Compare Source

v16.0.0

Compare Source

Features
  • Move @testing-library/dom and @types/react-dom to peer dependencies (#​1305) (a4744fa)
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

Compare Source

v15.0.6

Compare Source

v15.0.5

Compare Source

v15.0.4

Compare Source

v15.0.3

Compare Source

Bug Fixes
  • Don't raise TypeScript errors when hydating document (#​1304) (067d0c6)

v15.0.2

Compare Source

v15.0.1

Compare Source

v15.0.0

Compare Source

v14.3.1

Compare Source

Bug Fixes

v14.3.0

Compare Source

v14.2.2

Compare Source

v14.2.1

Compare Source

Bug Fixes
  • Update types to support all possible react component return values (#​1272) (55e79c2)

v14.2.0

Compare Source

Features
  • add reactStrictMode option to enable strict mode render (#​1241) (0880eba)

v14.1.2

Compare Source

Bug Fixes

v14.1.1

Compare Source

Bug Fixes

v14.1.0

Compare Source

Features

v14.0.0

Compare Source

Bug Fixes
Features
BREAKING CHANGES

v13.4.0

Compare Source

Features
  • renderHook: allow passing of all render options to renderHook (#​1118) (27a9584)

v13.3.0

Compare Source

Features

v13.2.0

Compare Source

Features

v13.1.1

Compare Source

Bug Fixes

v13.1.0

Compare Source

Features

v13.0.1

Compare Source

Bug Fixes

v13.0.0

Compare Source

Features
BREAKING CHANGES

Configuration

📅 Schedule: Branch creation - "before 4am on Monday" (UTC), 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 requested a review from a team as a code owner September 16, 2024 00:30
Copy link
Contributor Author

renovate bot commented Sep 16, 2024

⚠️ 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: @imgix/[email protected]
npm error Found: [email protected]
npm error node_modules/react
npm error   react@"^17.0.1" 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.1" 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-09-16T03_38_29_261Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-09-16T03_38_29_261Z-debug-0.log

Copy link

vercel bot commented Sep 16, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
contentful ✅ Ready (Inspect) Visit Preview 💬 Add feedback Sep 16, 2024 3:44am
contentful-staging ✅ Ready (Inspect) Visit Preview 💬 Add feedback Sep 16, 2024 3:44am

@renovate renovate bot enabled auto-merge (rebase) September 16, 2024 03:38
@renovate renovate bot force-pushed the renovate/major-testing-library-monorepo branch from 33e057f to ab4593d Compare September 16, 2024 03:38
@renovate renovate bot merged commit 5a32786 into main Sep 16, 2024
2 of 5 checks passed
@renovate renovate bot deleted the renovate/major-testing-library-monorepo branch September 16, 2024 03:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants