You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What happened:
NodeJS version 21 is going EOL in about 7 months at the time of writing.
Nevertheless, xeol doesn't pick it up when passing --lookahead 1y.
$ xeol --lookahead='1y' node:21-alpine
✔ EOL DB [no update available]
✔ Scanned for EOL [0 eol matches]
[0001] WARN failed to match cycle for distro Alpine Linux: <nil>
✅ no EOL software has been found
What you expected to happen:
I'd expect that xeol reports NodeJS 21 going EOL within one year.
How to reproduce it (as minimally and precisely as possible): xeol --lookahead='1y' node:21-alpine
Anything else we need to know?:
Scanning NodeJS images that include already EOL versions works fine, so the actual package detection seems to work fine.
$ xeol node:16-alpine
✔ EOL DB [no update available]
✔ Scanned for EOL [1 eol matches]
[0001] WARN failed to match cycle for distro Alpine Linux: <nil>
NAME VERSION EOL DAYS EOL TYPE
node 16.20.2 2023-09-11 60 binary
@noqcks Can confirm that passing --lookahead works now. Thanks for the quick fix. 🙏
$ xeol --lookahead='1y' node:21-alpine
✔ EOL DB [no update available]
✔ Scanned for EOL [1 eol matches]
[0002] WARN failed to match cycle for distro Alpine Linux: <nil>
NAME VERSION EOL DAYS EOL TYPE
node 21.1.0 2024-06-01 - binary
What happened:
NodeJS version 21 is going EOL in about 7 months at the time of writing.
Nevertheless, xeol doesn't pick it up when passing
--lookahead 1y
.What you expected to happen:
I'd expect that xeol reports NodeJS 21 going EOL within one year.
How to reproduce it (as minimally and precisely as possible):
xeol --lookahead='1y' node:21-alpine
Anything else we need to know?:
Scanning NodeJS images that include already EOL versions works fine, so the actual package detection seems to work fine.
Environment:
xeol version
: xeol 0.9.8cat /etc/os-release
or similar):The text was updated successfully, but these errors were encountered: