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.

Sign up for GitHub

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

Jump to bottom

chore(deps): update dependency chai to v5 #6078

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

chore(deps): update dependency chai to v5 #6078

wants to merge 1 commit into from
+2 −2

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 4, 2024 •
edited
Loading

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
chai (source) 4.5.0 -> 5.1.2 age adoption passing confidence
@types/chai (source) 4.3.20 -> 5.0.1 age adoption passing confidence

Release Notes

chaijs/chai (chai)

v5.1.2

Compare Source

What's Changed

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

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: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

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

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

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot added dependencies Pull requests that update a dependency file semver-major skip-change-log Do not include the PR in the change log in the release labels Jan 4, 2024
@renovate Renovate
Copy link
Contributor Author

renovate bot commented Jan 4, 2024 •
edited
Loading

⚠ 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 ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/chai
npm ERR!   dev chai@"5.1.0" from the root project
npm ERR!   peer chai@">=3.5.0" from [email protected]
npm ERR!   node_modules/karma-sinon-chai
npm ERR!     dev karma-sinon-chai@"2.0.2" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer chai@"^4.0.0" from [email protected]
npm ERR! node_modules/sinon-chai
npm ERR!   dev sinon-chai@"3.7.0" from the root project
npm ERR!   peer sinon-chai@">=2.9.0" from [email protected]
npm ERR!   node_modules/karma-sinon-chai
npm ERR!     dev karma-sinon-chai@"2.0.2" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/chai
npm ERR!   peer chai@"^4.0.0" from [email protected]
npm ERR!   node_modules/sinon-chai
npm ERR!     dev sinon-chai@"3.7.0" from the root project
npm ERR!     peer sinon-chai@">=2.9.0" from [email protected]
npm ERR!     node_modules/karma-sinon-chai
npm ERR!       dev karma-sinon-chai@"2.0.2" 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! See /tmp/renovate/cache/others/npm/eresolve-report.txt for a full report.

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

@renovate renovate bot force-pushed the renovate/chai-5.x branch 15 times, most recently from 5234771 to 43430dc Compare January 12, 2024 16:56
@renovate renovate bot force-pushed the renovate/chai-5.x branch 6 times, most recently from 1c7bda5 to 6afab93 Compare January 19, 2024 08:43
@renovate renovate bot force-pushed the renovate/chai-5.x branch 5 times, most recently from 35893d3 to bfd30a8 Compare January 23, 2024 20:05
@renovate renovate bot force-pushed the renovate/chai-5.x branch 3 times, most recently from 90665f8 to 4f6e8dc Compare November 4, 2024 22:01
@renovate renovate bot force-pushed the renovate/chai-5.x branch 14 times, most recently from f57531a to 9764f20 Compare November 14, 2024 19:35
@renovate renovate bot force-pushed the renovate/chai-5.x branch 11 times, most recently from f3c24ce to e703ae7 Compare November 20, 2024 01:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
dependencies Pull requests that update a dependency file semver-major skip-change-log Do not include the PR in the change log in the release
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@tjenkinson