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

Update dependency chai to v5 #319

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

Update dependency chai to v5 #319

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Dec 28, 2023

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
chai (source) 4.4.1 -> 5.1.2 age adoption passing confidence
@types/chai (source) 4.3.16 -> 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

v4.5.0

Compare Source


Configuration

📅 Schedule: Branch creation - "after 10pm every weekday,before 5am every weekday,every weekend" (UTC), Automerge - At any time (no schedule defined).

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

Rebasing: Whenever PR becomes conflicted, 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 Dec 28, 2023

⚠ 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: chai-as-promised@7.1.1
npm ERR! Found: chai@5.1.0
npm ERR! node_modules/chai
npm ERR!   dev chai@"5.1.0" from the root project
npm ERR!   peer chai@"*" from chai-spies@1.1.0
npm ERR!   node_modules/chai-spies
npm ERR!     dev chai-spies@"1.1.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer chai@">= 2.1.2 < 5" from chai-as-promised@7.1.1
npm ERR! node_modules/chai-as-promised
npm ERR!   dev chai-as-promised@"7.1.1" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: chai@4.4.1
npm ERR! node_modules/chai
npm ERR!   peer chai@">= 2.1.2 < 5" from chai-as-promised@7.1.1
npm ERR!   node_modules/chai-as-promised
npm ERR!     dev chai-as-promised@"7.1.1" 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-02-12T15_14_36_120Z-eresolve-report.txt

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

@renovate renovate bot force-pushed the renovate/chai-5.x branch from 7b4ddf5 to 752a585 Compare January 25, 2024 10:56
@renovate renovate bot force-pushed the renovate/chai-5.x branch from 752a585 to c3d5066 Compare February 12, 2024 15:14
@renovate renovate bot force-pushed the renovate/chai-5.x branch from c3d5066 to 72f0ee9 Compare May 9, 2024 10:58
@renovate renovate bot force-pushed the renovate/chai-5.x branch 2 times, most recently from 34afac4 to 188eb40 Compare June 13, 2024 01:28
@renovate renovate bot changed the title Update dependency chai to v5 Update dependency chai to v5 - autoclosed Jul 25, 2024
@renovate renovate bot closed this Jul 25, 2024
@renovate renovate bot deleted the renovate/chai-5.x branch July 25, 2024 14:07
@renovate renovate bot changed the title Update dependency chai to v5 - autoclosed Update dependency chai to v5 Jul 26, 2024
@renovate renovate bot reopened this Jul 26, 2024
@renovate renovate bot restored the renovate/chai-5.x branch July 26, 2024 11:22
@renovate renovate bot force-pushed the renovate/chai-5.x branch from 188eb40 to bd82f23 Compare September 24, 2024 22:09
@renovate renovate bot force-pushed the renovate/chai-5.x branch from bd82f23 to 99da5e8 Compare October 23, 2024 11:10
@renovate renovate bot force-pushed the renovate/chai-5.x branch from 99da5e8 to 3b74d53 Compare October 28, 2024 21:52
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