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 #789

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Mar 16, 2024

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: Enabled.

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.

Copy link
Contributor Author

renovate bot commented Mar 16, 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 could not resolve
npm error
npm error While resolving: sinon-chai@3.7.0
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
npm error Could not resolve dependency:
npm error peer chai@"^4.0.0" from sinon-chai@3.7.0
npm error node_modules/sinon-chai
npm error   dev sinon-chai@"3.7.0" from the root project
npm error
npm error Conflicting peer dependency: chai@4.4.1
npm error node_modules/chai
npm error   peer chai@"^4.0.0" from sinon-chai@3.7.0
npm error   node_modules/sinon-chai
npm error     dev sinon-chai@"3.7.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-05-08T16_57_30_154Z-eresolve-report.txt

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

@renovate renovate bot force-pushed the renovate/chai-5.x branch 13 times, most recently from 4bd8512 to 0138c04 Compare March 21, 2024 01:04
@renovate renovate bot force-pushed the renovate/chai-5.x branch 4 times, most recently from 9f779b2 to cd11375 Compare March 30, 2024 09:09
@renovate renovate bot force-pushed the renovate/chai-5.x branch 8 times, most recently from 193e9d7 to 0c67318 Compare April 8, 2024 21:35
@renovate renovate bot force-pushed the renovate/chai-5.x branch 4 times, most recently from 137c6b5 to 2df5727 Compare April 10, 2024 14:33
@renovate renovate bot force-pushed the renovate/chai-5.x branch 9 times, most recently from c388e40 to 71298b3 Compare October 31, 2024 22:54
@renovate renovate bot force-pushed the renovate/chai-5.x branch 3 times, most recently from f9574d3 to db840c0 Compare November 10, 2024 00:18
@renovate renovate bot force-pushed the renovate/chai-5.x branch 8 times, most recently from 2bf40ff to 8451a82 Compare November 26, 2024 07:33
@renovate renovate bot force-pushed the renovate/chai-5.x branch 4 times, most recently from 6353e00 to 9d5458b Compare December 3, 2024 21:36
@renovate renovate bot force-pushed the renovate/chai-5.x branch from 9d5458b to 0883504 Compare December 11, 2024 16:39
@renovate renovate bot force-pushed the renovate/chai-5.x branch 3 times, most recently from c35d5ba to f4a6c1d Compare January 3, 2025 11:33
@renovate renovate bot force-pushed the renovate/chai-5.x branch from f4a6c1d to 81674d3 Compare January 3, 2025 12:12
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