🚀 Feature Proposal

Hey all! Thanks for all the work on this project ❤

The last stable release for Jest (29.7) was Sep 2023. ~18 months ago.
It's been some time since v30 was initially in alpha and I was very excited to see@SimenB publish a new alpha7 in Jan 💯 🥳. There has also been a flurry of upstream nodejs improvements over the last few months, which are super exciting to see some of the collaboration in that area!

Given this, I wonder if there was a list of issues/blockers for a stable release of v30? I.e¹

• Are there specific issues that arerequired for v30 to be released? if so, which ones?
  • maybefeat(runtime): usecompileFunction overnew Script #15461 as mentioned, behind a flag?
• Are thereenhancements that the team wouldlike (but not blocking) v30 - if so which ones?
• Are contributions required/encouraged, if so which ones?²
• Is a stable release blocked on any upstream changes?
  • e.g.Add uninstall function evanw/node-source-map-support#339 +Mitigate memory leaks in jest-environment-node #15215 ?³

This would help have some more visibility and (hopefully?) some contributions as well. 🙏
I'm also curious to understand more of the current and future state of the project, but I will create a separate issue for that.

Thank you!

P.S - I have raised this as a feature, as the "questions" template lead to a community discord server, and I am not raising a bug. I suppose I "am" asking for afeature of a new v30 release 😅
Please let me know if there is a more appropriate template to use here 🙏

Motivation

I would like a v30 release, lots of nice fixes!

Example

No response

Pitch

N/A