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(deps): update testing-library monorepo (major) #401

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented May 6, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@testing-library/jest-dom ^5.16.4 -> ^6.0.0 age adoption passing confidence
@testing-library/react ^12.1.1 -> ^16.0.0 age adoption passing confidence

Release Notes

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

v6.6.3

Compare Source

v6.6.2

Compare Source

Bug Fixes

v6.6.1

Compare Source

v6.6.0

Compare Source

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 - "* 0-3 * * 1" in timezone America/New_York, 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.

Copy link
Contributor Author

renovate bot commented May 6, 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: @edx/frontend-component-footer-edx@1.0.0-semantically-released
npm error Found: react@17.0.2
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/react@15.0.6
npm error node_modules/@testing-library/react
npm error   dev @testing-library/react@"^15.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-05-06T04_05_56_792Z-eresolve-report.txt

npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-05-06T04_05_56_792Z-debug-0.log

@renovate renovate bot force-pushed the renovate/major-testing-library-monorepo branch from bd2140a to ce19d56 Compare May 13, 2024 10:30
Copy link
Contributor Author

renovate bot commented May 13, 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: @edx/frontend-component-footer-edx@1.0.0-semantically-released
npm error Found: react@17.0.2
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 || ^19.0.0" from @testing-library/react@16.1.0
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-12-16T12_41_59_117Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-12-16T12_41_59_117Z-debug-0.log

@renovate renovate bot force-pushed the renovate/major-testing-library-monorepo branch from ce19d56 to 59d3c94 Compare May 20, 2024 17:22
@renovate renovate bot force-pushed the renovate/major-testing-library-monorepo branch 2 times, most recently from 6488831 to 2042b34 Compare June 3, 2024 15:51
@renovate renovate bot force-pushed the renovate/major-testing-library-monorepo branch 2 times, most recently from c3d99cc to ee4ad21 Compare June 17, 2024 09:14
@renovate renovate bot force-pushed the renovate/major-testing-library-monorepo branch from ee4ad21 to beca452 Compare June 24, 2024 11:15
@renovate renovate bot force-pushed the renovate/major-testing-library-monorepo branch 2 times, most recently from 2e6efa9 to 82b1031 Compare July 8, 2024 11:12
@renovate renovate bot force-pushed the renovate/major-testing-library-monorepo branch 2 times, most recently from 4e0409b to 8b4d1e9 Compare July 22, 2024 08:01
@renovate renovate bot force-pushed the renovate/major-testing-library-monorepo branch 3 times, most recently from 62a0dc9 to 7fd8e6c Compare July 29, 2024 10:09
@renovate renovate bot force-pushed the renovate/major-testing-library-monorepo branch 6 times, most recently from 010258a to cd93e29 Compare August 12, 2024 09:38
@renovate renovate bot force-pushed the renovate/major-testing-library-monorepo branch 2 times, most recently from 3c402ac to 50bfaa6 Compare August 19, 2024 06:14
@renovate renovate bot force-pushed the renovate/major-testing-library-monorepo branch 2 times, most recently from dd75e6a to 32c09f2 Compare August 26, 2024 07:07
@renovate renovate bot force-pushed the renovate/major-testing-library-monorepo branch from 32c09f2 to a0dff68 Compare September 2, 2024 07:51
@renovate renovate bot force-pushed the renovate/major-testing-library-monorepo branch 2 times, most recently from deb5593 to dfe7b10 Compare September 16, 2024 09:33
@renovate renovate bot force-pushed the renovate/major-testing-library-monorepo branch 3 times, most recently from 57b6525 to 3321efa Compare September 23, 2024 11:24
@renovate renovate bot force-pushed the renovate/major-testing-library-monorepo branch 3 times, most recently from 86d31ac to 9e7e915 Compare October 2, 2024 08:18
@renovate renovate bot force-pushed the renovate/major-testing-library-monorepo branch 2 times, most recently from eea7d6b to f3df943 Compare October 14, 2024 06:30
@renovate renovate bot force-pushed the renovate/major-testing-library-monorepo branch from f3df943 to 91725b2 Compare October 21, 2024 06:27
@renovate renovate bot force-pushed the renovate/major-testing-library-monorepo branch 2 times, most recently from 73f6951 to cfdd37e Compare November 11, 2024 11:19
@renovate renovate bot force-pushed the renovate/major-testing-library-monorepo branch 2 times, most recently from d59c38e to c954c76 Compare November 25, 2024 10:32
@renovate renovate bot force-pushed the renovate/major-testing-library-monorepo branch 2 times, most recently from 2e9d847 to 42a6944 Compare December 2, 2024 08:56
@renovate renovate bot force-pushed the renovate/major-testing-library-monorepo branch 3 times, most recently from 7461d43 to 0de4ddf Compare December 9, 2024 16:55
@renovate renovate bot force-pushed the renovate/major-testing-library-monorepo branch from 0de4ddf to 90eb437 Compare December 16, 2024 09:46
@renovate renovate bot force-pushed the renovate/major-testing-library-monorepo branch from 90eb437 to 4c77d61 Compare December 16, 2024 12:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants