[Meta]: Current blockers for a v30 release?

[spanishpear]

🚀 Feature Proposal

Note

TLDR: I did some web + issue searching, and could not easily find information re: a jest roadmap, or a v30 release.
This issue seeks clarification on what is blocking or desired for a stable v30 release ❤

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 are required for v30 to be released? if so, which ones?
  • maybe feat(runtime): use compileFunction over new Script #15461 as mentioned, behind a flag?
• Are there enhancements that the team would like (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 a feature 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

Footnotes

1. Please note the examples here are purely examples from briefly looking at open issues/PRs, and I have no requirement/need for those specifically ❤, just trying to kickstart the convo! ↩

2. I could not find any contributions label, good first issue seems mostly stale ↩

3. Though, not sure if node-source-map-support is maintained/accepting PR's. ↩

[MillerSvt]

@SimenB Can you share your plans for the release date of the new version? Or is it a trade secret?)

[SimenB]

Hey!

Nothing secret 😀 I just haven't found the time to write a migration guide (I really should have done that as breaking changes were landing) or writing the blog post. I think code wise it's good to go.

There is a milestone (https://github.com/jestjs/jest/milestone/15), but we should probably just get the release out the door

[Solonotix]

I take that to mean Jest is still actively maintained? I was just coming by to check if it had been discontinued, because it seemed weird for Jest to have gone so long without an update, while React has made two huge changes in seemingly the same span of time. Granted, maybe that's related to why it hasn't had a release in that time.

[MillerSvt]

@SimenB Can you release my feature #15433 (and #15482) for v29.8.0? I need that, and it isn't a breaking change.

[khallmark]

@SimenB What do you need written exactly? I'll do it right now if we can ship Jest 30.

I do mean that literally.

[github-actions]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 30 days.

[MillerSvt]

Not stale

[khallmark]

@SimenB yo what do we need in order to ship a new version?

[khallmark]

@cpojer @orta @rickhanlonii Are any of you watching this project anymore?

[MillerSvt]

@SimenB @rickhanlonii @orta @cpojer Could you consider adding more people to help maintain this project? If you're unable to manage it alone, it appears the project might struggle to survive without additional support.