BREAKING: Upgrade Jest to v29

[legobeat]

#319 + #345 but rebased on next.

Blocked by

• BREAKING: Bump minimum Node.js version to ^14.15.0 #354
  • Release of deps/devDeps: bump semver to latest [CVE-2022-25883] #349

Version

Published prerelease version: v0.14.0-next.2

Changelog

🚀 Enhancement

• BREAKING: Upgrade Jest to v29 #348 (@yannbf @legobeat)
• BREAKING: Bump minimum Node.js version to ^14.15.0 #354 (@legobeat)
• Add waitForPageReady utility #361 (@yannbf)

🐛 Bug Fix

• Documentation: restructure docs and include more recipes #373 (@yannbf)
• Run nyc with correct packager manager command #364 (@ferdinandhummel-gph @yannbf)
• deps/devDeps: bump semver to latest [CVE-2022-25883] #349 (@legobeat)
• Make userAgent configurable #342 (@jaknas)
• devDeps: Bump auto from v10 to v11 #346 (@legobeat)
• CI: Fix yarn 2 issue #352 (@yannbf)
• chore: set engines.node to >=12.0.0 #351 (@legobeat)
• Maintenance: Update to yarn berry #344 (@yannbf)
• Maintenance: Remove csf upgrade in nightly check #343 (@yannbf)

🏠 Internal

• chore: disable yarn telemetry by default #350 (@legobeat)
• chore: dedupe dependency versions in yarn.lock #347 (@legobeat)

📝 Documentation

• Docs: Expand ejected config docs with an example #363 (@yannbf)

Authors: 4

• @ferdinandhummel-gph
• @legobeat
• Jakub Naskręski (@jaknas)
• Yann Braga (@yannbf)

[socket-security]

Updated and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Packages	Version	New capabilities	Transitives	Size	Publisher
jest-environment-node	28.1.3...29.7.0	None	+5/-8	218 kB	simenb
jest-runner	28.1.3...29.7.0	None	+22/-30	900 kB	simenb
jest	28.1.3...29.7.0	None	+39/-43	1.67 MB	simenb
babel-jest	28.1.3...29.7.0	None	+2/-8	30.5 kB	simenb
ts-jest	28.0.8...29.1.1	None	+40/-44	1.98 MB	kul
@types/jest	27.5.2...29.5.6	None	+6/-4	409 kB	types
jest-playwright-preset	2.0.0...3.0.1	None	+40/-44	1.74 MB	mxschmitt
jest-circus	28.1.3...29.7.0	None	+22/-26	1.04 MB	simenb
jest-junit	14.0.1...16.0.0	None	+0/-0	41.9 kB	jsonp
jest-image-snapshot	5.2.0...6.2.0	None	+40/-50	1.75 MB	amexopensource

🚮 Removed packages: @jest/[email protected]

[socket-security]

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Issue	Package	Version	Note	Source
New author	create-jest	29.7.0	New Author: simenb Previous Author: cpojer	@storybook/[email protected], [email protected], [email protected], [email protected], [email protected], [email protected] via package.json

Next steps

What is new author?

A new npm collaborator published a version of the package for the first time. New collaborators are usually benign additions to a project, but do indicate a change to the security surface area of a package.

Scrutinize new collaborator additions to packages because they now have the ability to publish code into your dependency tree. Packages should avoid frequent or unnecessary additions or changes to publishing rights.

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of package-name@version specifiers. e.g. @SocketSecurity ignore [email protected] bar@* or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore [email protected]

[kasperpeulen]

LGTM! cc @yannbf shall we release those PRs?

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (25cb18d) 76.66% compared to head (a4c6555) 76.66%.
Report is 2 commits behind head on next.

Additional details and impacted files

@@           Coverage Diff           @@
##             next     #348   +/-   ##
=======================================
  Coverage   76.66%   76.66%           
=======================================
  Files          11       11           
  Lines         180      180           
  Branches       40       40           
=======================================
  Hits          138      138           
  Misses         42       42           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[legobeat]

@kasperpeulen @yannbf Thank you both for tending to these!

Note on this one: As it is breaking (Jest v29 itself breaks Node.js v12), maybe you want to consider doing a maintenance release of current next before merging in the Jest v29 support?

Also esp #349

[legobeat]

I think in theory it should be possible to retain Node.js v12 compatibility - it woudl take some rework of the ci/tests though.
I'm hoping here that maintaining Node.js v12 compatibility in new versions isn't a prio nd dropping it here is fine..? 😺

[kasperpeulen]

Dropping node 12 is fine, storybook itself also doesn't support node 12 anymore.

[legobeat]

@kasperpeulen right, i was thinking for the benefit of downstreams as well as users who haven't upgraded yet, merging and releasing #349 first would be great.

So my proposed order would be #349 -> release -> #354 -> #348 (this PR)

WDYT?

[kasperpeulen]

@legobeat Sounds good to me.

@yannbf Let's do this when you are back.

[yannbf]

Hey there! Sorry for not checking this sooner. I'll update this PR and test it out next week!

[legobeat]

@yannbf Thanks! Just rebased on next and lifted #354 out of draft.

[github-actions]

🚀 PR was released in v0.14.0 🚀