-
Notifications
You must be signed in to change notification settings - Fork 1
chore(deps-dev): bump the testing group across 1 directory with 5 updates #420
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
Conversation
…ates Bumps the testing group with 5 updates in the / directory: | Package | From | To | | --- | --- | --- | | [@clerk/testing](https://github.com/clerk/javascript/tree/HEAD/packages/testing) | `1.12.8` | `1.13.1` | | [@playwright/mcp](https://github.com/microsoft/playwright-mcp) | `0.0.32` | `0.0.40` | | [@testing-library/jest-dom](https://github.com/testing-library/jest-dom) | `6.8.0` | `6.9.0` | | [jest](https://github.com/jestjs/jest/tree/HEAD/packages/jest) | `30.1.3` | `30.2.0` | | [jest-environment-node](https://github.com/jestjs/jest/tree/HEAD/packages/jest-environment-node) | `30.1.2` | `30.2.0` | Updates `@clerk/testing` from 1.12.8 to 1.13.1 - [Release notes](https://github.com/clerk/javascript/releases) - [Changelog](https://github.com/clerk/javascript/blob/main/packages/testing/CHANGELOG.md) - [Commits](https://github.com/clerk/javascript/commits/@clerk/testing@1.13.1/packages/testing) Updates `@playwright/mcp` from 0.0.32 to 0.0.40 - [Release notes](https://github.com/microsoft/playwright-mcp/releases) - [Commits](microsoft/playwright-mcp@v0.0.32...v0.0.40) Updates `@testing-library/jest-dom` from 6.8.0 to 6.9.0 - [Release notes](https://github.com/testing-library/jest-dom/releases) - [Changelog](https://github.com/testing-library/jest-dom/blob/main/CHANGELOG.md) - [Commits](testing-library/jest-dom@v6.8.0...v6.9.0) Updates `jest` from 30.1.3 to 30.2.0 - [Release notes](https://github.com/jestjs/jest/releases) - [Changelog](https://github.com/jestjs/jest/blob/main/CHANGELOG.md) - [Commits](https://github.com/jestjs/jest/commits/v30.2.0/packages/jest) Updates `jest-environment-node` from 30.1.2 to 30.2.0 - [Release notes](https://github.com/jestjs/jest/releases) - [Changelog](https://github.com/jestjs/jest/blob/main/CHANGELOG.md) - [Commits](https://github.com/jestjs/jest/commits/v30.2.0/packages/jest-environment-node) --- updated-dependencies: - dependency-name: "@clerk/testing" dependency-version: 1.13.1 dependency-type: direct:development update-type: version-update:semver-minor dependency-group: testing - dependency-name: "@playwright/mcp" dependency-version: 0.0.40 dependency-type: direct:development update-type: version-update:semver-patch dependency-group: testing - dependency-name: "@testing-library/jest-dom" dependency-version: 6.9.0 dependency-type: direct:development update-type: version-update:semver-minor dependency-group: testing - dependency-name: jest dependency-version: 30.2.0 dependency-type: direct:development update-type: version-update:semver-minor dependency-group: testing - dependency-name: jest-environment-node dependency-version: 30.2.0 dependency-type: direct:development update-type: version-update:semver-minor dependency-group: testing ... Signed-off-by: dependabot[bot] <support@github.com>
|
View your CI Pipeline Execution ↗ for commit 01d983e
☁️ Nx Cloud last updated this comment at |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nx Cloud has identified a possible root cause for your failed CI:
The test failure is occurring due to the dependency update of @testing-library/jest-dom from version 6.8.0 to 6.9.0. The error "ReferenceError: Node is not defined" is coming from within the updated package itself, specifically at line 1984:4 of the jest-dom library's internal matchers file.
This failure is classified as 'environment_state' because:
- The failure is not caused by any code changes in the pull request - this is purely a dependency update PR from Dependabot
- The error originates from within an external dependency (@testing-library/jest-dom@6.9.0) rather than from any application code
- This represents a package compatibility issue where the updated dependency has introduced an incompatibility with the current test environment configuration
- The failure is occurring in the test setup phase when importing the jest-dom library, indicating an environmental configuration mismatch
Since this is an environmental issue caused by a dependency incompatibility rather than application code changes, no code modifications are warranted. The failure should be addressed by either:
- Rolling back to the previous compatible version of @testing-library/jest-dom (6.8.0)
- Updating the test environment configuration to be compatible with the new version
- Waiting for a patch release that fixes the compatibility issue
This type of failure is common in dependency upgrade scenarios and falls squarely into the environmental state category rather than requiring application code fixes.
A code change would likely not resolve this issue, so no action was taken.
⚙️ An Nx Cloud workspace admin can disable these reviews in workspace settings.
|
❌ Test Failure Detected This Dependabot PR is failing CI tests due to a breaking change in Auto-merge will NOT proceed - this PR requires manual investigation before merging. Options:
Closing this PR for now. We can revisit when the library issue is resolved or test environment is updated. |
|
Closing due to test failures from breaking changes in @testing-library/jest-dom@6.9.0. Will revisit when library is fixed or test environment is updated. |
|
This pull request was built based on a group rule. Closing it will not ignore any of these versions in future pull requests. To ignore these dependencies, configure ignore rules in dependabot.yml |
Bumps the testing group with 5 updates in the / directory:
1.12.81.13.10.0.320.0.406.8.06.9.030.1.330.2.030.1.230.2.0Updates
@clerk/testingfrom 1.12.8 to 1.13.1Release notes
Sourced from
@clerk/testing's releases.Changelog
Sourced from
@clerk/testing's changelog.Commits
e552532ci(repo): Version packages (#6868)5720787ci(repo): Version packages (#6844)090ca74feat(clerk-js,nextjs,clerk-react,testing,types,vue): UserAvatar component (#6...b6ed9dafix(testing): Update dependency dotenv to v17.2.2 (#6832)Updates
@playwright/mcpfrom 0.0.32 to 0.0.40Release notes
Sourced from
@playwright/mcp's releases.... (truncated)
Commits
a86b580chore: mark v0.0.40 (#1079)927e570chore: roll Playwright to latest (#1078)24e68fadevops: do not use npm token (#1076)e503227devops: merge canary publishing workflow into publish.yml (#1075)711089dchore: add auth token example (#1070)4a7be8ddevops: migrate to OIDC NPM publishing (#1068)1523338feat(config): add sharedBrowserContext option to reuse browser context across...08bd91dchore: mark v0.0.39 (#1059)ef83729chore: roll Playwright to latest (#1060)a70854cchore: roll Playwright to latest (#1056)Maintainer changes
This version was pushed to npm by [GitHub Actions](https://www.npmjs.com/~GitHub Actions), a new releaser for
@playwright/mcpsince your current version.Updates
@testing-library/jest-domfrom 6.8.0 to 6.9.0Release notes
Sourced from
@testing-library/jest-dom's releases.Commits
95f870afeat: Add .toAppearBefore/.toAppearAfter matcher (#702)d6663f5docs: add nossbigg as a contributor for code, and test (#703)Updates
jestfrom 30.1.3 to 30.2.0Release notes
Sourced from jest's releases.
Changelog
Sourced from jest's changelog.
Commits
855864ev30.2.0Updates
jest-environment-nodefrom 30.1.2 to 30.2.0Release notes
Sourced from jest-environment-node's releases.
Changelog
Sourced from jest-environment-node's changelog.
Commits
855864ev30.2.0Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditions