Skip to content

chore(deps): update dependency chai to v5 - autoclosed#264

Closed
renovate[bot] wants to merge 1 commit intomasterfrom
renovate/chai-5.x
Closed

chore(deps): update dependency chai to v5 - autoclosed#264
renovate[bot] wants to merge 1 commit intomasterfrom
renovate/chai-5.x

Conversation

@renovate
Copy link

@renovate renovate bot commented Jan 25, 2024

This PR contains the following updates:

Package Change Age Confidence
chai (source) 4.3.4 -> 5.3.1 age confidence

Release Notes

chaijs/chai (chai)

v5.3.1

Compare Source

v5.3.0

Compare Source

v5.2.2

Compare Source

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

v4.5.0

Compare Source

What's Changed

Full Changelog: chaijs/chai@v4.4.1...v4.5.0

v4.4.1

Compare Source

What's Changed

Full Changelog: chaijs/chai@v4.4.0...v4.4.1

v4.4.0

Compare Source

What's Changed

Full Changelog: chaijs/chai@v4.3.10...v4.4.0

v4.3.10

Compare Source

This release simply bumps all dependencies to their latest non-breaking versions.

What's Changed

Full Changelog: chaijs/chai@v4.3.9...v4.3.10

v4.3.9

Compare Source

Upgrade dependencies.

This release upgrades dependencies to address CVE-2023-43646 where a large function name can cause "catastrophic backtracking" (aka ReDOS attack) which can cause the test suite to hang.

Full Changelog: chaijs/chai@v4.3.8...v4.3.9

v4.3.8

Compare Source

What's Changed

New Contributors

Full Changelog: chaijs/chai@v4.3.7...v4.3.8

v4.3.7

Compare Source

What's Changed

Full Changelog: chaijs/chai@v4.3.6...v4.3.7

v4.3.6

Compare Source

Update loupe to 2.3.1

v4.3.5

Compare Source


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 this update 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 bot force-pushed the renovate/chai-5.x branch from f711025 to 141a488 Compare January 25, 2024 12:18
@renovate renovate bot force-pushed the renovate/chai-5.x branch from 141a488 to 4e0e8e7 Compare February 12, 2024 15:10
@renovate renovate bot force-pushed the renovate/chai-5.x branch from 4e0e8e7 to 0193ae6 Compare May 9, 2024 10:51
@renovate renovate bot changed the title chore(deps): update dependency chai to v5 chore(deps): 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:52
@renovate renovate bot changed the title chore(deps): update dependency chai to v5 - autoclosed chore(deps): 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 12:47
@renovate renovate bot force-pushed the renovate/chai-5.x branch from 0193ae6 to 348efb9 Compare October 23, 2024 10:32
@renovate renovate bot force-pushed the renovate/chai-5.x branch from 348efb9 to 74be74e Compare February 14, 2025 22:21
@renovate renovate bot force-pushed the renovate/chai-5.x branch from 74be74e to 1627717 Compare July 8, 2025 19:52
@renovate
Copy link
Author

renovate bot commented Jul 8, 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

@renovate renovate bot force-pushed the renovate/chai-5.x branch from 1627717 to c4bfcc5 Compare August 18, 2025 12:43
@renovate renovate bot changed the title chore(deps): update dependency chai to v5 chore(deps): update dependency chai to v5 - autoclosed Aug 22, 2025
@renovate renovate bot closed this Aug 22, 2025
@renovate renovate bot deleted the renovate/chai-5.x branch August 22, 2025 15:11
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