🛡️ Sentinel: Fix EOL detection for older and odd Node.js versions #812
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR updates the End-of-Life (EOL) detection logic in
src/index.tsto accurately identify older and odd-numbered Node.js versions as EOL.Previously,
checkEOLonly returned true if the major version existed in theEOL_DATESmap and the current date was past the EOL date. The map only contained recent even-numbered LTS versions (18, 20, 22, 24). This meant that:The fix:
major < 12to instantly flag ancient versions as EOL.EOL_DATESto include dates for Node 12, 14, 16, 18, 20, 22, 24, and odd versions 19, 21, 23, 25.This ensures that security tools and consumers relying on
isEOLget accurate information about the security status of the Node.js runtime.PR created automatically by Jules for task 16069661776977529000 started by @srod
Summary by cubic
Fix EOL detection so older and odd-numbered Node.js versions are correctly flagged as End-of-Life. This removes false “supported” results and ensures accurate security status for isEOL consumers.
Written for commit 4dd5bd0. Summary will update on new commits.