refactor(chore): remove Node js 20 support#161
Conversation
rohit-sourcefuse
left a comment
There was a problem hiding this comment.
Node 20 removal and the workflow/matrix changes look clean. One thing to fix before merge: package.json sets engines.node to "22 || 24", but the regenerated package-lock.json root still has ">=22" — the lockfile was generated before the engines value was changed and not re-run. Re-run npm install so they match.
Suggestion: standardize on ">=22" for a published library — "22 || 24" excludes Node 23 and every future LTS (26, 28…), so the package would refuse to install on the next LTS until another bump. Don't over-constrain consumers. Checks are green otherwise.
remove Node js 20 support BREAKING CHANGE: yes GH-160
SonarQube reviewer guideSummary: Drop Node.js 20 support and bump to version 8.1.0, updating engine requirement to Node.js 22 or 24 only. Review Focus: The main change is reducing Node.js version support from 20, 22, and 24 down to just 22 and 24. Verify this aligns with project requirements and that no dependencies have critical issues with Node.js 20 removal. The large package-lock.json changes reflect typical dependency updates; focus on any breaking changes in key packages like Helmet, Express, and LoopBack components. Start review at:
|
rohit-sourcefuse
left a comment
There was a problem hiding this comment.
Engines and lockfile now match (22 || 24 both sides) and all checks are green. Approving — thanks for the quick turnaround.
|
🎉 This PR is included in version 9.0.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |



remove Node js 20 support
BREAKING CHANGE:
yes
GH-160
Description
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Fixes # (issue)
Checklist:
Build:
Test: