-
-
Notifications
You must be signed in to change notification settings - Fork 772
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
docs: overview of compatible nodejs versions #2601
Comments
Finding historic versions for Node is indeed a good case. I guess we could try to reflect this somehow. Maybe we should have a little unit test that checks the versions running on CI are the same ones listed. Not sure how to keep it in sync otherwise. |
Thanks for the PR. I supplied feedback on #2602 last week. |
Thanks for the feedback. |
It's possible to automate like this in our pipeline. This is how to extract the major versions:
So this would be sufficient to get the Node versions supported during a build:
Do you want to have a stab at how this could be used to automate updating some table or similarly? |
Is your feature request related to a problem? Please describe.
The support docs states that the current LTS nodejs is supported.
For projects that are slower to upgrade the node version, it is difficult to find the correct sinon version, as the current LTS version is newer than the old one required by the projects. Currently it is difficult to find out which sinon version supports an old node version.
Describe the solution you'd like
Simple table which states which is the minimum supported node version for every mayor sinon version.
Describe alternatives you've considered
As alternative re-add and maintain engines attribute in package.json for upcoming releases. Was removed in #1608.
Additional context
nope
The text was updated successfully, but these errors were encountered: