Skip to content

chore(deps): update dependency chai-exclude to v3 #2540

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

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Apr 25, 2025

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
chai-exclude 2.1.1 -> 3.0.1 age adoption passing confidence

Release Notes

mesaugat/chai-exclude (chai-exclude)

v3.0.1

Compare Source

  • Fix bug with date objects not working properly #​54 #​55

v3.0.0

Compare Source

  • BREAKING: chai-exclude is now an ESM package
  • Supports chai v5 and above #​51

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 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 was generated by Mend Renovate. View the repository job log.

Copy link
Contributor Author

renovate bot commented Apr 25, 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 warn Unknown env config "store". This will stop working in the next major version of npm.
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: @cucumber/[email protected]
npm error Found: [email protected]
npm error node_modules/chai
npm error   dev chai@"4.5.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer chai@">= 5" from [email protected]
npm error node_modules/chai-exclude
npm error   dev chai-exclude@"3.0.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 /runner/cache/others/npm/_logs/2025-05-09T06_19_58_100Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-05-09T06_19_58_100Z-debug-0.log

@renovate renovate bot added the 🤖 dependencies Dependency upgrade label Apr 25, 2025
@renovate renovate bot force-pushed the renovate/chai-exclude-3.x branch 3 times, most recently from 9b9e6a8 to a7eb1ce Compare April 30, 2025 08:32
@renovate renovate bot force-pushed the renovate/chai-exclude-3.x branch 5 times, most recently from c1d035a to 62cb3b8 Compare May 7, 2025 10:37
@renovate renovate bot force-pushed the renovate/chai-exclude-3.x branch from 62cb3b8 to 28ea66f Compare May 9, 2025 06:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🤖 dependencies Dependency upgrade
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants