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

svc-secops · 2024-04-18T13:54:30Z

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@testing-library/jest-dom	`^4.2.4` -> `^6.0.0`
@testing-library/react	`^9.3.2` -> `^16.0.0`
@testing-library/user-event	`^7.1.2` -> `^14.0.0`

Release Notes

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

`v6.6.3`

Compare Source

Bug Fixes

add vitest import when extending vitest matchers (#646) (5ba0156)

`v6.6.2`

Compare Source

Bug Fixes

remove recursive type reference in vitest types (#636) (4468378)

`v6.6.1`

Compare Source

Bug Fixes

fix lodash import in to-have-selection.js (#642) (ced792e)

`v6.6.0`

Compare Source

Features

implement toHaveSelection (#637) (9b14804)

`v6.5.0`

Compare Source

Features

toHaveValue: Asserting aria-valuenow (#479) (acbf416)

`v6.4.8`

Compare Source

Bug Fixes

Drop peerDependencies from package.json (#610) (faf534b)

`v6.4.7`

Compare Source

Bug Fixes

Type definition of toHaveClass (#611) (5cc6298)

Bug Fixes

add js suffix to isEqualWith import (#599) (e8c8b13)

`v6.4.4`

Compare Source

Bug Fixes

infra: codecoverage token addition (#600) (f03a582)

`v6.4.3`

Compare Source

Bug Fixes

Updates role support for aria-required attribute in toBeRequired (#590) (20aca33)

`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

Add toHaveRole matcher (#572) (f7dc673)

`v6.3.0`

Compare Source

Features

Support for regular expressions in toHaveClass (#563) (9787ed5)

`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

Upgrade @adobe/css-tools to v4.3.2 (#553) (b64b953)

`v6.1.5`

Compare Source

Bug Fixes

support uppercase custom props in toHaveStyle (#552) (b7b7c6a)

`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

proper @jest/globals import (#530) (5b492ac)

`v6.1.2`

Compare Source

Bug Fixes

bump @adobe/css-tools for ESM support (#525) (b959a68)

`v6.1.1`

Compare Source

Bug Fixes

package.json: update main and module file paths (#523) (853a3e5)

`v6.1.0`

Compare Source

Features

Publish ESM and CJS (https://github.com/testing-library/jest-dom/pull/519)

`v6.0.1`

Compare Source

Bug Fixes

matchers type is making the global expect unsafe (#513) (bdb34f1)

`v6.0.0`

Compare Source

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

`v5.17.0`

Compare Source

Features

New toHaveAccessibleErrorMessage better implementing the spec, deprecate toHaveErrorMessage (#503) (d717c66)

`v5.16.5`

Compare Source

Bug Fixes

migrate ccs v3 to @adobe/css-tools v4 (#470) (948d90f)

`v5.16.4`

Compare Source

Bug Fixes

Support unenclosed inner text for details elements in to be visible (#396) (af18453)

`v5.16.3`

Compare Source

Bug Fixes

clarify toHaveFocus message when using .not (#447) (6988a67)

`v5.16.2`

Compare Source

Bug Fixes

add custom element support to toBeDisabled (#368) (8162115)

`v5.16.1`

Compare Source

Bug Fixes

Improve toHaveClass error message format (#405) (a9beb47)

`v5.16.0`

Compare Source

Features

Update aria-query to 5.0.0 (#414) (de26c7a)

`v5.15.1`

Compare Source

Bug Fixes

wrong deprecate error message (#422) (dfcefa2)

`v5.15.0`

Compare Source

Features

import parse directly from css (#415) (4cb606c)

`v5.14.1`

Compare Source

Bug Fixes

Updates deprecated matchers info (#378) (fc9ce6d)

`v5.14.0`

Compare Source

Features

toHaveAccessibleName and toHaveAccessibleDescription (#377) (87ffd2a)

`v5.13.0`

Compare Source

Features

Add toHaveErrorMessage matcher (#370) (217fdcc)

`v5.12.0`

Compare Source

Features

check for any Node in toHaveTextContent (#358) (fa0d91d)

`v5.11.10`

Compare Source

Bug Fixes

normalize expected value in toContainHTML (#349) (21ad89b), closes #347

`v5.11.9`

Compare Source

Bug Fixes

Ignore comment nodes in toBeEmptyDOMElement (#317) (6a6531d)

`v5.11.8`

Compare Source

Bug Fixes

Adds expected text for toContainHTML checks that fail (#299) (#318) (0bd1ed9)

`v5.11.7`

Compare Source

Bug Fixes

check equality in toHaveDisplayValue (fix #290) (#319) (4179117)

`v5.11.6`

Compare Source

Bug Fixes

Improved error messaging for toHaveFocus assertion (#304) (c79faa2)

`v5.11.5`

Compare Source

Bug Fixes

treat shadow DOM elements as in the document (#298) (7ee54ab)

`v5.11.4`

Compare Source

Bug Fixes

do not explicitly depend on jest assertion utils (#250) (2da8c71)

`v5.11.3`

Compare Source

Bug Fixes

Changed toHaveStyle to use getPropertyValue instead of accessing the property directly (#285) (92176e1)

`v5.11.2`

Compare Source

Bug Fixes

Suggest using toBeEmptyDOMElement instead of toBeEmpty (#284) (2cd17d3)

`v5.11.1`

Compare Source

Bug Fixes

toHaveStyle: strictly match empty values (#276) (5bea350), closes #272

`v5.11.0`

Compare Source

Features

extend toBeChecked to support any role that's compatible (#267) (c135d0b)

`v5.10.1`

Compare Source

Bug Fixes

element not allowed to be disabled being returned as disabled (#261) (5e39222)

`v5.10.0`

Compare Source

Features

[toBeValid/toBeInvalid] Check aria-invalid on any element (#259) (14d1630)

`v5.9.0`

Compare Source

Features

Deprecate toBeEmpty in favour of toBeEmptyDomElement (#216) (#254) (927c5a4)

`v5.8.0`

Compare Source

Features

add toBePartiallyChecked matcher (#249) (e46299b)

`v5.7.0`

Compare Source

Features

Allow to use regex on toHaveDisplayValue (#242) (5c9e8e5)

`v5.6.0`

Compare Source

Features

Add new custom matcher toHaveDescription (#244) (943a0c9)

`v5.5.0`

Compare Source

Features

Add toHaveDisplayValue() matcher (#223) (840414f)

`v5.4.0`

Compare Source

Features

add switch role to toBeChecked (#228) (144c647)

`v5.3.0`

Compare Source

Features

add exact mode option for toHaveClass (#176) (#217) (cc8721e)

`v5.2.0`

Compare Source

Features

toHaveValue: Enhanced error message with type information… (#219) (eb51c17)

`v5.1.1`

Compare Source

Bug Fixes

root matchers module (closes #197) (#200) (3b98d4d)

`v5.1.0`

Compare Source

Features

Enhance toHaveStyle to accept JS as css (#196) (7921e4a)

`v5.0.2`

Compare Source

Bug Fixes

toBeVisible ignoring Details element (#184) (e4d61c2)

`v5.0.1`

Compare Source

Bug Fixes

Add @types/testing-library__jest-dom dependency (#189) (030da62), closes #123 #160 #185

`v5.0.0`

Compare Source

Remove extend-expect typings (#182) (c76f8c5), closes #182

BREAKING CHANGES

moving typings to @types/testing-library__jest-dom
This version does not includes types. The next patch release v5.0.1 will. If you need the type definitions please do not update to v.5.0.0.

testing-library/react-testing-library (@testing-library/react)

`v16.0.1`

Compare Source

Bug Fixes

Add support for exactOptionalPropertyTypes in TypeScript (#1351) (3dcd8a9)

`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

Bug Fixes

Ensure act is not any when React.act is not declared (#1323) (c1f2957)

`v15.0.6`

Compare Source

Bug Fixes

export new act when available (#1319) (b6e59f7)

`v15.0.5`

Compare Source

Bug Fixes

Stop restricting container option based on hydrate (#1313) (d143f46)

`v15.0.4`

Compare Source

Bug Fixes

Ensure renderHook options extend options for render (#1308) (48282c2)

`v15.0.3`

Compare Source

Bug Fixes

Don't raise TypeScript errors when hydating document (#1304) (067d0c6)

`v15.0.2`

Compare Source

Bug Fixes

Improve legacyRoot error message (#1301) (c63b873)

`v15.0.1`

Compare Source

Bug Fixes

Stop using nullish coalescing (#1299) (1645d21)

`v15.0.0`

Compare Source

Release

15.0.0 (#1295) (787cb85)

BREAKING CHANGES

Minimum supported Node.js version is 18.0
New version of @testing-library/dom changes various roles. Check out the changed tests in testing-library/dom-testing-library@2c57055 to get an overview about what changed.

`v14.3.1`

Compare Source

Bug Fixes

Stop using nullish coalescing (#1300) (8434a24)

`v14.3.0`

Compare Source

Features

Add support for React 19 Canary (#1294) (9c4a46d)

`v14.2.2`

Compare Source

Bug Fixes

Remove unused types (#1287) (3da62fd)

`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

revert missing hooks warnings (#1255) (1c67477)

`v14.1.1`

Compare Source

Bug Fixes

log globals warning only once (#1252) (fd52a59), closes #1249

`v14.1.0`

Compare Source

Features

add warnings when globals are missing (#1244) (d80319f)

`v14.0.0`

Compare Source

Bug Fixes

Prevent "missing act" warning for queued microtasks (#1137) (f78839b)

Features

Bump @testing-library/dom to 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`

Compare Source

Features

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

`v13.3.0`

Compare Source

Features

Use globalThis if available (#1070) (c80809a)

`v13.2.0`

Compare Source

Features

Export RenderHookOptions type (#1062) (46b28ad)

`v13.1.1`

Compare Source

Bug Fixes

TS: export interface RenderHookResult (#1049) (9171163)

`v13.1.0`

Compare Source

Features

Add renderHook (#991) (9535eff)

`v13.0.1`

Compare Source

Bug Fixes

Specify a non-* version for @types/react-dom (#1040) (2a889e8)

`v13.0.0`

Compare Source

Features

Add support for React 18 (#1031) (ccd8a0d)

BREAKING CHANGES

Drop support for React 17 and earlier. We'll use the new createRoot API 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.

`v12.1.5`

Compare Source

Bug Fixes

Only supports React < 18 (#1041) (9e2b5db)

`v12.1.4`

Compare Source

Bug Fixes

Match runtime type of baseElement in TypeScript types (#1023) (96ed8da)

`v12.1.3`

Compare Source

Bug Fixes

Add @types/react-dom as a direct dependency (#1001) (149d9a9)

`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

TS: make wrapper allow a simple function comp (#966) (cde904c)

`v12.1.0`

Compare Source

Features

improve JSDocs for RenderOptions (#909) (fbacb0d)

`v12.0.0`

Compare Source

Bug Fixes

Bump testing-library/dom to v8 alpha (#923) (770246e)
Update @testing-library/dom (#931) (05c7421)

Features

Bump @testing-library/dom (6e6bf85)
Drop support for node 10 (#930) (42dad78)

BREAKING CHANGES

Bump @testing-library/dom to 8.0.0. Please check out the @testing-library/[email protected] release page for a detailed list of breaking changes.
node 10 is no longer supported. It reached its end-of-life on 30.04.2021.

`v11.2.7`

Compare Source

Bug Fixes

Guard against process not being defined (#911) (8a1c8e9)

`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

render: add default type for Queries parameter (#871) (5576e6f)

`v11.2.4`

Compare Source

Bug Fixes

render: Default to HTMLElement in returned container (#868) (81c2de9)

`v11.2.3`

Compare Source

Bug Fixes

Return type of unmount is void (#857) (1389f09)

`v11.2.2`

Compare Source

Bug Fixes

dependencies: bump dom testing library (#836) (7fcb0f2)

`v11.2.1`

Compare Source

Bug Fixes

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

`v11.2.0`

Compare Source

Features

bump dom testing library (#831) (456424f)

`v11.1.2`

Compare Source

Bug Fixes

import pretty-format from @testing-library/dom (#821) ([2712dc2](https://redirect.github.com/testing-library/react-testing-li

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - "after 8am and before 4pm on tuesday" in timezone Etc/UTC.

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, 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 has been generated by Renovate Bot.

svc-secops · 2024-04-18T13:54:32Z

⚠ Artifact update problem

Renovate failed to update artifacts 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: final/client/package-lock.json

npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @testing-library/[email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/jest
npm ERR!   dev jest@"^27.5.1" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peerOptional jest@">= 28" from @testing-library/[email protected]
npm ERR! node_modules/@testing-library/jest-dom
npm ERR!   dev @testing-library/jest-dom@"^6.0.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/jest
npm ERR!   peerOptional jest@">= 28" from @testing-library/[email protected]
npm ERR!   node_modules/@testing-library/jest-dom
npm ERR!     dev @testing-library/jest-dom@"^6.0.0" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! 
npm ERR! For a full report see:
npm ERR! /tmp/renovate/cache/others/npm/_logs/2024-04-18T13_54_15_432Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-04-18T13_54_15_432Z-debug-0.log

File name: client/package-lock.json

npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @testing-library/[email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/jest
npm ERR!   dev jest@"^27.5.1" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peerOptional jest@">= 28" from @testing-library/[email protected]
npm ERR! node_modules/@testing-library/jest-dom
npm ERR!   dev @testing-library/jest-dom@"^6.0.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/jest
npm ERR!   peerOptional jest@">= 28" from @testing-library/[email protected]
npm ERR!   node_modules/@testing-library/jest-dom
npm ERR!     dev @testing-library/jest-dom@"^6.0.0" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! 
npm ERR! For a full report see:
npm ERR! /tmp/renovate/cache/others/npm/_logs/2024-04-18T13_54_21_833Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-04-18T13_54_21_833Z-debug-0.log

svc-secops · 2024-06-08T13:25:23Z

⚠️ Artifact update problem

Renovate failed to update artifacts 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: final/client/package-lock.json

npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @testing-library/[email protected]
npm error Found: [email protected]
npm error node_modules/jest
npm error   dev jest@"^27.5.1" from the root project
npm error
npm error Could not resolve dependency:
npm error peerOptional jest@">= 28" from @testing-library/[email protected]
npm error node_modules/@testing-library/jest-dom
npm error   dev @testing-library/jest-dom@"^6.0.0" from the root project
npm error
npm error Conflicting peer dependency: [email protected]
npm error node_modules/jest
npm error   peerOptional jest@">= 28" from @testing-library/[email protected]
npm error   node_modules/@testing-library/jest-dom
npm error     dev @testing-library/jest-dom@"^6.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-06-08T13_25_10_466Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-06-08T13_25_10_466Z-debug-0.log

File name: client/package-lock.json

npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @testing-library/[email protected]
npm error Found: [email protected]
npm error node_modules/jest
npm error   dev jest@"^27.5.1" from the root project
npm error
npm error Could not resolve dependency:
npm error peerOptional jest@">= 28" from @testing-library/[email protected]
npm error node_modules/@testing-library/jest-dom
npm error   dev @testing-library/jest-dom@"^6.0.0" from the root project
npm error
npm error Conflicting peer dependency: [email protected]
npm error node_modules/jest
npm error   peerOptional jest@">= 28" from @testing-library/[email protected]
npm error   node_modules/@testing-library/jest-dom
npm error     dev @testing-library/jest-dom@"^6.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-06-08T13_25_15_471Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-06-08T13_25_15_471Z-debug-0.log

svc-secops requested a review from a team as a code owner April 18, 2024 13:54

svc-secops added the dependencies Pull requests that update a dependency file label Apr 18, 2024

chore(deps): update testing-library monorepo

e5d5bce

svc-secops force-pushed the renovate/major-testing-library-monorepo branch from 3453ae5 to e5d5bce Compare June 8, 2024 13:25

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

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

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

svc-secops commented Apr 18, 2024 •

edited

Loading

svc-secops commented Apr 18, 2024

svc-secops commented Jun 8, 2024

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

Are you sure you want to change the base?

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

Conversation

svc-secops commented Apr 18, 2024 • edited Loading

Release Notes

Bug Fixes

Bug Fixes

Bug Fixes

Features

Features

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Features

Features

Bug Fixes

Features

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Features

Bug Fixes

Features

BREAKING CHANGES

Features

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Features

Bug Fixes

Features

Bug Fixes

Features

Features

Features

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Features

Bug Fixes

Features

Features

Features

Features

Features

Features

Features

Features

Features

Bug Fixes

Features

Bug Fixes

Bug Fixes

BREAKING CHANGES

Bug Fixes

Features

BREAKING CHANGES

Bug Fixes

svc-secops commented Apr 18, 2024 •

edited

Loading