Skip to content

Conversation

@krypton-build-user
Copy link
Collaborator

@krypton-build-user krypton-build-user commented Sep 1, 2025

This PR contains the following updates:

Package Type Update Change
chai (source) devDependencies major 4.5.0 -> 6.2.2

Release Notes

chaijs/chai (chai)

v6.2.2

Compare Source

What's Changed

New Contributors

Full Changelog: chaijs/chai@v6.2.1...v6.2.2

v6.2.1

Compare Source

What's Changed

New Contributors

Full Changelog: chaijs/chai@v6.2.0...v6.2.1

v6.2.0

Compare Source

What's Changed

Full Changelog: chaijs/chai@v6.1.0...v6.2.0

v6.1.0

Compare Source

What's Changed

Full Changelog: chaijs/chai@v6.0.2...v6.1.0

v6.0.1

Compare Source

What's Changed

Full Changelog: chaijs/chai@v6.0.0...v6.0.1

v6.0.0

Compare Source

BREAKING CHANGES

Chai is now bundled into a single file. The lib/*.js files are no longer present, and so any code that imports those files directly will need to change. The only file that can be imported now is ./index.js.

What's Changed

Full Changelog: chaijs/chai@v5.3.2...v6.0.0

v5.3.3

Compare Source

What's Changed

Full Changelog: chaijs/chai@v5.3.2...v5.3.3

v5.3.2

Compare Source

Reverts the removal of the bundled version of chai in 5.3.1

What's Changed

Full Changelog: chaijs/chai@v5.3.1...v5.3.2

v5.3.1

Compare Source

What's Changed

Full Changelog: chaijs/chai@v5.3.0...v5.3.1

v5.3.0

Compare Source

What's Changed

Full Changelog: chaijs/chai@v5.2.2...v5.3.0

v5.2.2

Compare Source

What's Changed

Full Changelog: chaijs/chai@v5.2.1...v5.2.2

v5.2.1

Compare Source

What's Changed

Mostly internal changes but @​SuperchupuDev realised the package.json engines field was out of date, so it has been updated to reflect that v5.0.0 onwards only supports Node >=18.

New Contributors

Full Changelog: chaijs/chai@v5.2.0...v5.2.1

v5.2.0

Compare Source

What's Changed

New Contributors

Full Changelog: chaijs/chai@v5.1.2...v5.2.0

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 - "* 0-3 1 * *" (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 this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Self-Hosted Renovate Bot. Find all logs here.

@krypton-build-user
Copy link
Collaborator Author

krypton-build-user commented Sep 1, 2025

⚠️ 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@6.2.2
npm ERR! node_modules/chai
npm ERR!   dev chai@"6.2.2" 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.5.0
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! See /tmp/renovate/cache/others/npm/eresolve-report.txt for a full report.

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants