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) #491

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Apr 22, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@testing-library/jest-dom 5.17.0 -> 6.6.3 age adoption passing confidence
@testing-library/react 10.4.9 -> 16.1.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.1.0

Compare Source

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

v12.1.5

Compare Source

Bug Fixes

v12.1.4

Compare Source

Bug Fixes
  • Match runtime type of baseElement in TypeScript types (#​1023) (96ed8da)

v12.1.3

Compare Source

Bug Fixes

v12.1.2

Compare Source

Bug Fixes
  • render: Don't reject wrapper types based on statics (#​973) (7f53b56)

v12.1.1

Compare Source

Bug Fixes

v12.1.0

Compare Source

Features

v12.0.0

Compare Source

Bug Fixes
Features
BREAKING CHANGES

v11.2.7

Compare Source

Bug Fixes

v11.2.6

Compare Source

Bug Fixes
  • types: exclude tsconfig from types folder in publish flow (#​893) (58150b9)

v11.2.5

Compare Source

Bug Fixes

v11.2.4

Compare Source

Bug Fixes
  • render: Default to HTMLElement in returned container (#​868) (81c2de9)

v11.2.3

Compare Source

Bug Fixes

v11.2.2

Compare Source

Bug Fixes

v11.2.1

Compare Source

Bug Fixes
  • types: Allow all HTML and SVG elements in render. (#​833) (1dc33b2)

v11.2.0

Compare Source

Features

v11.1.2

Compare Source

Bug Fixes

v11.1.1

Compare Source

Bug Fixes

v11.1.0

Compare Source

Features

v11.0.4

Compare Source

Bug Fixes
  • Trigger ongot-/onlostpointercapture when calling got-/lostpointercapture (#​786) (c546a6f)

v11.0.3

Compare Source

Bug Fixes
  • Trigger onPointerEnter/Leave when calling pointerEnter/Leave (#​784) (c7b5622)

v11.0.2

Compare Source

Bug Fixes

v11.0.1

Compare Source

Bug Fixes

v11.0.0

Compare Source

Features
  • use act to flush instead of custom implementation (#​768) (693228c)
BREAKING CHANGES
  • cleanup is now synchronous and wraps the unmounting process in act.

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 Apr 22, 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/[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@"15.0.7" 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-07T14_57_40_588Z-eresolve-report.txt

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

@renovate renovate bot enabled auto-merge (rebase) April 22, 2024 06:18
@renovate renovate bot force-pushed the renovate/major-testing-library-monorepo branch 5 times, most recently from 87b6e28 to 40bc640 Compare April 29, 2024 08:52
@renovate renovate bot force-pushed the renovate/major-testing-library-monorepo branch 6 times, most recently from 1358b6d to 28f7583 Compare May 7, 2024 14:57
@renovate renovate bot force-pushed the renovate/major-testing-library-monorepo branch from 28f7583 to 1deabb9 Compare May 13, 2024 09:53
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/[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 || ^19.0.0" from @testing-library/[email protected]
npm error node_modules/@testing-library/react
npm error   dev @testing-library/react@"16.1.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-09T17_21_41_269Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-12-09T17_21_41_269Z-debug-0.log

@renovate renovate bot force-pushed the renovate/major-testing-library-monorepo branch 3 times, most recently from 3cb663c to 8e8efd1 Compare May 27, 2024 09:45
@renovate renovate bot force-pushed the renovate/major-testing-library-monorepo branch 2 times, most recently from ba6a8c3 to c8a1973 Compare June 3, 2024 15:47
@renovate renovate bot force-pushed the renovate/major-testing-library-monorepo branch 3 times, most recently from d9c65d8 to f41e7c9 Compare June 17, 2024 15:00
@renovate renovate bot force-pushed the renovate/major-testing-library-monorepo branch 3 times, most recently from ffbd519 to a29f656 Compare July 1, 2024 07:00
@renovate renovate bot force-pushed the renovate/major-testing-library-monorepo branch 2 times, most recently from ee78f68 to ddddda4 Compare July 22, 2024 07:37
@renovate renovate bot force-pushed the renovate/major-testing-library-monorepo branch from ddddda4 to 95cdc1e Compare July 22, 2024 10:20
@renovate renovate bot force-pushed the renovate/major-testing-library-monorepo branch from d06f0a1 to ca102a0 Compare September 2, 2024 11:08
@renovate renovate bot force-pushed the renovate/major-testing-library-monorepo branch from ca102a0 to da2daeb Compare September 9, 2024 12:30
@renovate renovate bot force-pushed the renovate/major-testing-library-monorepo branch 3 times, most recently from 50c95ff to 9b45eb1 Compare September 23, 2024 10:26
@renovate renovate bot force-pushed the renovate/major-testing-library-monorepo branch 4 times, most recently from 6d45b67 to 4a7b74d Compare October 1, 2024 13:21
@renovate renovate bot force-pushed the renovate/major-testing-library-monorepo branch 2 times, most recently from 9fb9816 to ff5dd26 Compare October 14, 2024 07:54
@renovate renovate bot force-pushed the renovate/major-testing-library-monorepo branch 5 times, most recently from 1941128 to b4fb7db Compare October 22, 2024 16:19
@renovate renovate bot force-pushed the renovate/major-testing-library-monorepo branch 4 times, most recently from 9e8d30c to 566dda6 Compare November 4, 2024 09:17
@renovate renovate bot force-pushed the renovate/major-testing-library-monorepo branch 3 times, most recently from 6958526 to a5de81e Compare November 18, 2024 06:00
@renovate renovate bot force-pushed the renovate/major-testing-library-monorepo branch 2 times, most recently from 0bf0027 to 2934226 Compare November 25, 2024 11:16
@renovate renovate bot force-pushed the renovate/major-testing-library-monorepo branch 2 times, most recently from 71e85c3 to b6486f8 Compare December 5, 2024 22:39
@renovate renovate bot force-pushed the renovate/major-testing-library-monorepo branch from b6486f8 to 108f47c Compare December 9, 2024 12:33
@renovate renovate bot force-pushed the renovate/major-testing-library-monorepo branch from 108f47c to df2365a Compare December 9, 2024 17:21
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