Skip to content
This repository has been archived by the owner on Dec 12, 2024. It is now read-only.

Update dependency chai to v5 #289

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

Update dependency chai to v5 #289

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Oct 12, 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

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

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

@renovate Renovate
Copy link
Contributor Author

renovate bot commented Oct 12, 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: javascript/pfi-aud-usd-tbdex/package-lock.json
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: [email protected]
npm error Found: [email protected]
npm error node_modules/chai
npm error   dev chai@"5.1.2" from the root project
npm error   peer chai@">= 2.1.2 < 6" from [email protected]
npm error   node_modules/chai-as-promised
npm error     dev chai-as-promised@"8.0.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer chai@"^4.1.2" from [email protected]
npm error node_modules/chai-string
npm error   dev chai-string@"1.5.0" from the root project
npm error
npm error Conflicting peer dependency: [email protected]
npm error node_modules/chai
npm error   peer chai@"^4.1.2" from [email protected]
npm error   node_modules/chai-string
npm error     dev chai-string@"1.5.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-10-29T22_58_56_546Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-10-29T22_58_56_546Z-debug-0.log

@renovate renovate bot added the dependencies Pull requests that update a dependency file label Oct 12, 2024
@renovate renovate bot force-pushed the renovate/chai-5.x branch 6 times, most recently from e911261 to 7958524 Compare October 23, 2024 10:37
@renovate renovate bot force-pushed the renovate/chai-5.x branch 3 times, most recently from c37f3a4 to 692b8c2 Compare October 28, 2024 23:19
@renovate renovate bot force-pushed the renovate/chai-5.x branch from 692b8c2 to a549c57 Compare October 29, 2024 22:59
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Reviewers

@michaelneale michaelneale Awaiting requested review from michaelneale michaelneale is a code owner

@mistermoe mistermoe Awaiting requested review from mistermoe mistermoe is a code owner

@jiyoonie9 jiyoonie9 Awaiting requested review from jiyoonie9

@acekyd acekyd Awaiting requested review from acekyd acekyd is a code owner

Assignees
No one assigned
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
0 participants