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

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.0 age adoption passing confidence

Release Notes

chaijs/chai (chai)

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 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 added the dependencies Dependency updates, removals or additions label Dec 29, 2023
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: [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! 
npm ERR! Could not resolve dependency:
npm ERR! peer chai@">= 2.1.2 < 5" from [email protected]
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: [email protected]
npm ERR! node_modules/chai
npm ERR!   peer chai@">= 2.1.2 < 5" from [email protected]
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_27_00_747Z-eresolve-report.txt

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

@renovate renovate bot force-pushed the renovate/chai-5.x branch 2 times, most recently from 9431c45 to d36bd18 Compare January 13, 2024 11:27
@renovate renovate bot force-pushed the renovate/chai-5.x branch from d36bd18 to c0ec108 Compare January 25, 2024 10:12
@renovate renovate bot force-pushed the renovate/chai-5.x branch from c0ec108 to f555618 Compare February 12, 2024 15:27
@github-actions github-actions bot added the chore Internal changes not visible to the user label Feb 12, 2024
@renovate renovate bot changed the title chore(deps): update dependency chai to v5 chore(deps): update dependency chai to v5 - autoclosed Apr 19, 2024
@renovate renovate bot closed this Apr 19, 2024
@renovate renovate bot deleted the renovate/chai-5.x branch April 19, 2024 13:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
chore Internal changes not visible to the user dependencies Dependency updates, removals or additions
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants