-
-
Notifications
You must be signed in to change notification settings - Fork 3k
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
📌 Mocha 11 Release Plan #5249
Comments
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
How're you feeling about merging #5148? It'd be nice to be able to kick the tires on |
Feeling very good about it 😄. Merged!
You raise a good point about Thanksgiving. I'm personally going to be out of commission for something like half the week. 🦃 My tentative plan (not run by @Uzlopak or @voxpelli, cc for input) is to release Mocha@11 as stable on Monday, December 2nd. |
For what it's worth, I upgraded mocha-remote to the v11.0.0 release and ran test without any issues 👍 |
|
I've upgraded as well, and encountered no problems. Thanks! |
@JoshuaKGoldberg sounds like we can close this one? ;) Congrats! |
Haha I was thinking of keeping it open a bit for visibility. But every notification that comes up on it does strike fear of breakages in me... let's say next week I'll close it unless some big breakage happens. |
Edit (December 2nd, 2024):
mocha@11.0.1
is released aslatest
on npm.We're working on a new major version of Mocha! 📦
Mocha 11 will be the first new major version of Mocha in 3 years. It will contain no new bug fixes or features compared to v10. The only user-facing changes in Mocha 11 will be:
Our plan is to:
mocha@11.0.0
is published asmocha@next
on npm 👍As mentioned in #5027, we're a new volunteer maintenance team and want to tread carefully with breaking changes to Mocha. We're holding off an adding any additional breaking changes until the next major version, Mocha 12, which we will not release until some time in 2025 at the earliest. We'll first learn see how the Mocha 11 release goes and learn from it. As careful as we are planning on being with Mocha 11, there is always some risk with publishing a new major version of a project. Mocha is depended upon by thousands upon thousands of consuming projects, many of which are not open source or built in ways we're familiar with as a team.
Alternating major versions between ones that purely raise engine targets and ones that add breaking feature changes is a strategy used by some other ecosystem projects, such as typescript-eslint.
The text was updated successfully, but these errors were encountered: