Upgrade ava: 4.3.3 → 5.1.1 (major)

depfu[bot] commented 1 year ago

Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ ava (4.3.3 → 5.1.1) · Repo

Release Notes

5.1.1

What's Changed

Fix de-registration of shared workers to ensure AVA exits correctly, by @codetheweb in #3149 & #3151

Full Changelog: v5.1.0...v5.1.1

5.1.0

What's Changed

Output logs for tests that remain pending when AVA exits by @kevo1ution in #3125

Check for --config file extensions after they fail to load, allowing custom loaders by @panva in #3135

New Contributors

@kevo1ution made their first contribution in #3125

@panva made their first contribution in #3135

Full Changelog: v5.0.1...v5.1.0

5.0.1

Despite the major version bump this is a relatively minor release. Node.js 12 is no longer supported. The type definitions are now distributed to be compatible with TypeScript 4.7 or newer.
npm install --save-dev ava
Breaking Changes

AVA now requires Node.js 14.19, 16.15 or 18. #3043

Type definition distribution assumes at least TypeScript 4.7. #3041

We're now exporting types rather than interfaces. #3096

Improvements

Detect process.exit() called from tests by @gibson042 in #3080

Improve test result accessibility by @gibson042 in #3082

Parse for line numbers with latest supported ECMA version by @novemberborn in #3063

Work around os.cpus() returning an empty array on unsupported platforms by @catink123 in #3095

Count timeouts separately from the timed out tests by @novemberborn in #3099

Cap idle timeouts to the maximum possible value by @creestor in #3100

New Contributors

@Prinzhorn made their first contribution in #3073

@catink123 made their first contribution in #3095

@creestor made their first contribution in #3100

@DavidVujic made their first contribution in #3109

Full Changelog: v4.3.3...v5.0.1

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 23 commits:

Depfu Status

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands

@depfu rebase
Rebases against your default branch and redoes this update

@depfu recreate
Recreates this PR, overwriting any edits that you've made to it

@depfu merge
Merges this PR once your tests are passing and conflicts are resolved

@depfu close
Closes this PR and deletes the branch

@depfu reopen
Restores the branch and reopens this PR (if it's closed)

@depfu pause
Ignores all future updates for this dependency and closes this PR

@depfu pause [minor|major]
Ignores all future minor/major updates for this dependency and closes this PR

@depfu resume
Future versions of this dependency will create PRs again (leaves this PR as is)

vercel[bot] commented 1 year ago

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated
next-api-handler	❌ Failed (Inspect)			Jan 22, 2023 at 9:11PM (UTC)

codeclimate[bot] commented 1 year ago

Code Climate has analyzed commit 07b43b13 and detected 0 issues on this pull request.

View more on Code Climate.

cypress[bot] commented 1 year ago

Test summary

11 • 0 • 0 • 0

Run details


Project	next-api-handler
Status	Passed
Commit	07b43b13f9
Started	Jan 22, 2023 9:13 PM
Ended	Jan 22, 2023 9:13 PM
Duration	00:11 💡
OS	Linux Debian - 11.4
Browser	Electron 102

View run in Cypress Dashboard ➡️

This comment has been generated by cypress-bot as a result of this project's GitHub integration settings. You can manage this integration in this project's settings in the Cypress Dashboard

depfu[bot] commented 1 year ago

Closed in favor of #71.

Howard86 / next-api-handler