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 dependency chai to v5 #4683

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Dec 29, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
chai (source) 4.4.1 -> 5.1.1 age adoption passing confidence

Release Notes

chaijs/chai (chai)

v5.1.1

Compare Source

What's Changed

New Contributors

Full Changelog: chaijs/chai@v5.1.0...v5.1.1

v5.1.0

Compare Source

What's Changed

New Contributors

Full Changelog: chaijs/chai@v5.0.3...v5.1.0

v5.0.3

Compare Source

Fix bad v5.0.2 publish.

Full Changelog: chaijs/chai@v5.0.2...v5.0.3

v5.0.2

Compare Source

What's Changed

Full Changelog: chaijs/chai@v5.0.1...v5.0.2

v5.0.0

Compare Source

BREAKING CHANGES

  • Chai now only supports EcmaScript Modules (ESM). This means your tests will need to either have import {...} from 'chai' or import('chai'). require('chai') will cause failures in nodejs. If you're using ESM and seeing failures, it may be due to a bundler or transpiler which is incorrectly converting import statements into require calls.
  • Dropped support for Internet Explorer.
  • Dropped support for NodeJS < 18.
  • Minimum supported browsers are now Firefox 100, Safari 14.1, Chrome 100, Edge 100. Support for browsers prior to these versions is "best effort" (bug reports on older browsers will be assessed individually and may be marked as wontfix).

What's Changed

New Contributors

Full Changelog: chaijs/chai@4.3.1...v5.0.0


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot enabled auto-merge (squash) December 29, 2023 11:13
Copy link
Contributor Author

renovate bot commented Dec 29, 2023

⚠ 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: package-lock.json
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: chai-as-promised@7.1.1
npm error Found: chai@5.1.0
npm error node_modules/chai
npm error   dev chai@"5.1.0" from the root project
npm error   peer chai@">=1.9.0" from chai-jest-snapshot@2.0.0
npm error   node_modules/chai-jest-snapshot
npm error     dev chai-jest-snapshot@"2.0.0" from the root project
npm error   1 more (karma-chai)
npm error
npm error Could not resolve dependency:
npm error peer chai@">= 2.1.2 < 5" from chai-as-promised@7.1.1
npm error node_modules/chai-as-promised
npm error   dev chai-as-promised@"7.1.1" from the root project
npm error
npm error Conflicting peer dependency: chai@4.4.1
npm error node_modules/chai
npm error   peer chai@">= 2.1.2 < 5" from chai-as-promised@7.1.1
npm error   node_modules/chai-as-promised
npm error     dev chai-as-promised@"7.1.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-05-08T01_04_44_031Z-eresolve-report.txt

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

File name: e2e/package-lock.json
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: chai-as-promised@7.1.1
npm error Found: chai@5.1.0
npm error node_modules/chai
npm error   dev chai@"5.1.0" from the root project
npm error   peer chai@">=1.9.0" from chai-jest-snapshot@2.0.0
npm error   node_modules/chai-jest-snapshot
npm error     dev chai-jest-snapshot@"2.0.0" from the root project
npm error   1 more (karma-chai)
npm error
npm error Could not resolve dependency:
npm error peer chai@">= 2.1.2 < 5" from chai-as-promised@7.1.1
npm error node_modules/chai-as-promised
npm error   dev chai-as-promised@"7.1.1" from the root project
npm error
npm error Conflicting peer dependency: chai@4.4.1
npm error node_modules/chai
npm error   peer chai@">= 2.1.2 < 5" from chai-as-promised@7.1.1
npm error   node_modules/chai-as-promised
npm error     dev chai-as-promised@"7.1.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-05-08T01_04_50_290Z-eresolve-report.txt

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

@renovate renovate bot force-pushed the renovate/chai-5.x branch 20 times, most recently from c731955 to 9e04e22 Compare February 1, 2024 04:36
@renovate renovate bot force-pushed the renovate/chai-5.x branch 7 times, most recently from 745918a to 9332128 Compare February 5, 2024 22:38
@renovate renovate bot force-pushed the renovate/chai-5.x branch 7 times, most recently from a722200 to 5aaec55 Compare April 19, 2024 02:14
@renovate renovate bot force-pushed the renovate/chai-5.x branch 7 times, most recently from 331dbc0 to 2069e79 Compare April 25, 2024 18:14
@renovate renovate bot force-pushed the renovate/chai-5.x branch 8 times, most recently from 995ecfa to 4e68b32 Compare May 6, 2024 00:14
@renovate renovate bot force-pushed the renovate/chai-5.x branch 5 times, most recently from 89a989c to 6d983a4 Compare May 8, 2024 01:04
Copy link
Contributor Author

renovate bot commented May 9, 2024

⚠️ 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: package-lock.json
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: chai-as-promised@7.1.1
npm error Found: chai@5.1.1
npm error node_modules/chai
npm error   dev chai@"5.1.1" from the root project
npm error   peer chai@">=1.9.0" from chai-jest-snapshot@2.0.0
npm error   node_modules/chai-jest-snapshot
npm error     dev chai-jest-snapshot@"2.0.0" from the root project
npm error   1 more (karma-chai)
npm error
npm error Could not resolve dependency:
npm error peer chai@">= 2.1.2 < 5" from chai-as-promised@7.1.1
npm error node_modules/chai-as-promised
npm error   dev chai-as-promised@"7.1.1" from the root project
npm error
npm error Conflicting peer dependency: chai@4.4.1
npm error node_modules/chai
npm error   peer chai@">= 2.1.2 < 5" from chai-as-promised@7.1.1
npm error   node_modules/chai-as-promised
npm error     dev chai-as-promised@"7.1.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-05-09T11_19_36_910Z-eresolve-report.txt

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

File name: e2e/package-lock.json
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: chai-as-promised@7.1.1
npm error Found: chai@5.1.1
npm error node_modules/chai
npm error   dev chai@"5.1.1" from the root project
npm error   peer chai@">=1.9.0" from chai-jest-snapshot@2.0.0
npm error   node_modules/chai-jest-snapshot
npm error     dev chai-jest-snapshot@"2.0.0" from the root project
npm error   1 more (karma-chai)
npm error
npm error Could not resolve dependency:
npm error peer chai@">= 2.1.2 < 5" from chai-as-promised@7.1.1
npm error node_modules/chai-as-promised
npm error   dev chai-as-promised@"7.1.1" from the root project
npm error
npm error Conflicting peer dependency: chai@4.4.1
npm error node_modules/chai
npm error   peer chai@">= 2.1.2 < 5" from chai-as-promised@7.1.1
npm error   node_modules/chai-as-promised
npm error     dev chai-as-promised@"7.1.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-05-09T11_19_44_356Z-eresolve-report.txt

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

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.

None yet

1 participant