The repo currently uses Node.js 16 in multiple workflows and actions, as well as several outdated npm packages. Node.js 16 reached EOL on September 11, 2023 , which means there wont be any new security updates or patches , also there would be Potential compatibility issues with newer dependencies
Additionally, the fallback logic in get-node-version-from-package-lock action still references Node.js 14 (EOL in April 2023) and Node.js 18 (EOL in April 2025).
After updating these will verify if workflows still function correctly after updates
Yes I am willing to submit a PR!
The repo currently uses Node.js 16 in multiple workflows and actions, as well as several outdated npm packages. Node.js 16 reached EOL on September 11, 2023 , which means there wont be any new security updates or patches , also there would be Potential compatibility issues with newer dependencies
Additionally, the fallback logic in
get-node-version-from-package-lockaction still references Node.js 14 (EOL in April 2023) and Node.js 18 (EOL in April 2025).After updating these will verify if workflows still function correctly after updates
Yes I am willing to submit a PR!