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

Update chai to v5 (major) #371

Closed
wants to merge 1 commit into from
Closed

Conversation

balena-renovate[bot]
Copy link
Contributor

@balena-renovate balena-renovate bot commented Jun 19, 2024

This PR contains the following updates:

Package Type Update Change
@types/chai (source) devDependencies major ^4.3.14 -> ^5.0.0
chai (source) devDependencies major ^4.4.1 -> ^5.0.0

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

v4.5.0

Compare Source

What's Changed

Full Changelog: chaijs/chai@v4.4.1...v4.5.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 is behind base branch, 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 has been generated by Renovate Bot.

Copy link
Contributor Author

balena-renovate bot commented Jun 19, 2024

⚠️ 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 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.0.0" 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@"^7.1.1" from the root project
npm error
npm error Could not resolve dependency:
npm error peer chai@"2 - 4" from [email protected]
npm error node_modules/chai-like
npm error   dev chai-like@"^1.1.1" from the root project
npm error
npm error Conflicting peer dependency: [email protected]
npm error node_modules/chai
npm error   peer chai@"2 - 4" from [email protected]
npm error   node_modules/chai-like
npm error     dev chai-like@"^1.1.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 /tmp/renovate/cache/others/npm/_logs/2024-09-27T19_51_11_708Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-09-27T19_51_11_708Z-debug-0.log

@balena-renovate balena-renovate bot changed the title Update dependency chai to v5 Update dependency chai to v5 - autoclosed Jul 25, 2024
@balena-renovate balena-renovate bot closed this Jul 25, 2024
@balena-renovate balena-renovate bot deleted the renovate/major-5-chai branch July 25, 2024 12:56
@balena-renovate balena-renovate bot changed the title Update dependency chai to v5 - autoclosed Update dependency chai to v5 Jul 26, 2024
@balena-renovate balena-renovate bot restored the renovate/major-5-chai branch July 26, 2024 10:50
@balena-renovate balena-renovate bot reopened this Jul 26, 2024
@balena-renovate balena-renovate bot force-pushed the renovate/major-5-chai branch from 128522b to 1099669 Compare July 26, 2024 11:50
Update @types/chai from 4.3.16 to 5.0.0

Change-type: patch
@balena-renovate balena-renovate bot force-pushed the renovate/major-5-chai branch from 1099669 to 8a50852 Compare September 27, 2024 19:51
@balena-renovate balena-renovate bot changed the title Update dependency chai to v5 Update chai to v5 (major) Sep 27, 2024
@Page- Page- closed this Nov 3, 2024
Copy link
Contributor Author

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 5.x releases. But if you manually upgrade to 5.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.

@balena-renovate balena-renovate bot deleted the renovate/major-5-chai branch November 3, 2024 12:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant