-
Notifications
You must be signed in to change notification settings - Fork 61
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
Breaking change accidentally release in 10.4.0 #351
Comments
Thanks for reporting. I’ve downgraded |
Ah, thank you for the follow up. I didn't notice the minimum Node.js version. (Node.js v16 is no longer supported and everyone should migrate to v18 or later, though.) BTW, this package specifies eslint-plugin-mocha/package.json Line 6 in a936f2a
|
The |
Things look good now with I haven't looked closely over the timing of various changes, etc, but was surprised it was not caught in the CI tests given that you had a matrix of all supported engines set up: Anyways, thanks again!!! You can close this, IMO. |
Hi there - love this package and thanks for all the hard work!
There is a problem with your latest release of
10.4.0
however:10.4.0
ofeslint-plugin-mocha
added the"globals": "^14.0.0"
dependency.globals@14.0.0
has a node engines requirement of>=18
.eslint-plugin-mocha
v10.4.0
still has an engines requirement of>=14.0.0
(though it seems like you're moving towards 20 as evidenced by what's inmain
).This is an accidentally breaking change for projects (like one of ours) that are running on Node 16, with a dependency of something like
"eslint-plugin-mocha": "^10.2.0"
I'm not sure what you're using from
globals
, but it seems like13
is compatible with Node>=8
, so you can probably just change your dependency to some version of 13 and be ok, or perhaps with minor changes.Would you consider fixing things in a patch of some sort in the
10.x
semver realm?The text was updated successfully, but these errors were encountered: