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 - autoclosed #238

Closed
wants to merge 1 commit into 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 - "after 10pm,before 5:00am" in timezone America/Vancouver, 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 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.

Copy link
Contributor Author

renovate bot commented Dec 29, 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! 
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-04-24T07_14_27_401Z-eresolve-report.txt

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

@renovate renovate bot force-pushed the renovate/chai-5.x branch 6 times, most recently from 29ec829 to 5a25e71 Compare January 6, 2024 09:12
@renovate renovate bot force-pushed the renovate/chai-5.x branch 5 times, most recently from df7a74c to 179c944 Compare January 10, 2024 10:41
@renovate renovate bot force-pushed the renovate/chai-5.x branch 11 times, most recently from f5636ad to 8fdf935 Compare January 20, 2024 06:37
@renovate renovate bot force-pushed the renovate/chai-5.x branch 6 times, most recently from 3cb820f to 40766df Compare January 31, 2024 09:06
@renovate renovate bot force-pushed the renovate/chai-5.x branch from 40766df to 2ca78f5 Compare February 2, 2024 12:27
@renovate renovate bot force-pushed the renovate/chai-5.x branch 3 times, most recently from 9b9a694 to 937bf9f Compare March 27, 2024 09:47
@renovate renovate bot force-pushed the renovate/chai-5.x branch 5 times, most recently from d100c70 to 3fe8099 Compare March 30, 2024 11:53
@renovate renovate bot force-pushed the renovate/chai-5.x branch 2 times, most recently from b4bbae5 to db94fa9 Compare April 24, 2024 07:14
@renovate renovate bot force-pushed the renovate/chai-5.x branch from db94fa9 to 889a2a8 Compare May 9, 2024 14:03
Copy link
Contributor Author

renovate bot commented May 9, 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: 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
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-07-04T07_23_24_450Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-07-04T07_23_24_450Z-debug-0.log

@renovate renovate bot force-pushed the renovate/chai-5.x branch 3 times, most recently from 5df2511 to 072e21f Compare May 10, 2024 06:39
@renovate renovate bot force-pushed the renovate/chai-5.x branch 4 times, most recently from a86947c to 8f51347 Compare May 22, 2024 06:28
@renovate renovate bot force-pushed the renovate/chai-5.x branch from 8f51347 to 0567d66 Compare June 4, 2024 06:29
@renovate renovate bot force-pushed the renovate/chai-5.x branch 3 times, most recently from b633bc8 to 798ab0e Compare June 12, 2024 06:30
@renovate renovate bot force-pushed the renovate/chai-5.x branch from 798ab0e to dd57340 Compare July 4, 2024 07:10
@renovate renovate bot force-pushed the renovate/chai-5.x branch from dd57340 to f0576c6 Compare July 4, 2024 07:23
@KazuCocoa
Copy link
Member

#315

@KazuCocoa KazuCocoa closed this Jul 9, 2024
@renovate renovate bot changed the title chore(deps): update dependency chai to v5 chore(deps): update dependency chai to v5 - autoclosed Jul 9, 2024
@renovate renovate bot deleted the renovate/chai-5.x branch July 9, 2024 05:27
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.

1 participant