Skip to content
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

🧹 Versioning: Bump version ranges to just about Node LTS #5206

Open
JoshuaKGoldberg opened this issue Sep 3, 2024 · 0 comments · May be fixed by #5216
Open

🧹 Versioning: Bump version ranges to just about Node LTS #5206

JoshuaKGoldberg opened this issue Sep 3, 2024 · 0 comments · May be fixed by #5216
Assignees
Labels
semver-major implementation requires increase of "major" version number; "breaking changes" status: accepting prs Mocha can use your help with this one!
Milestone

Comments

@JoshuaKGoldberg
Copy link
Member

Overview

We're gearing up for a new major version of Mocha 11. That means we can bump the minimum Node engine version! Hooray! This is great for a couple of reasons:

We'd like to bump to, at the most strict, Node LTS. An added pressure is that Mocha is still used by large projects such as ESLint and TypeScript, which have older version support requirements.

Our current thought is to go with:

@JoshuaKGoldberg JoshuaKGoldberg added the semver-major implementation requires increase of "major" version number; "breaking changes" label Sep 3, 2024
@JoshuaKGoldberg JoshuaKGoldberg added this to the v11.0.0 milestone Sep 3, 2024
@JoshuaKGoldberg JoshuaKGoldberg self-assigned this Sep 3, 2024
@JoshuaKGoldberg JoshuaKGoldberg added the status: accepting prs Mocha can use your help with this one! label Sep 3, 2024
@voxpelli voxpelli linked a pull request Sep 16, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
semver-major implementation requires increase of "major" version number; "breaking changes" status: accepting prs Mocha can use your help with this one!
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant