-
Notifications
You must be signed in to change notification settings - Fork 4
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
feat: Add support for Node v18.14.2 #10
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To me it seems ok. I was just wondering whether it’s worth it also to adjust the GH workflows to support that scenario until we remove it
Good point. I've adjusted the version. |
package.json
Outdated
"node": "^20.11.0 || >=21.2.0", | ||
"npm": ">= 10" | ||
"node": "^18.14.2 || ^20.11.0 || >=21.2.0", | ||
"npm": ">= 9" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
if we wanna use the provenance statements. we have to use >=9.5.0 https://docs.npmjs.com/generating-provenance-statements#prerequisites
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
node 18.14.2 was the first release with npm 9.5.0 support. so we should be fine. But we could be more restrictive here by setting it to >= 9.5.0
, right?
https://github.com/nodejs/node/blob/main/doc/changelogs/CHANGELOG_V18.md#18.14.2
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done
Please adjust also the "requirement"section in the readme, regarding the minimal versions https://github.com/SAP/ui5-linter?tab=readme-ov-file#requirements |
No description provided.