Open Brianm0823 opened 4 months ago
Sounds good to me. We need to define our EoL strategy first, then we can post a file there.
This would be awesome!
Essentially, https://endoflife.date/api/valkey/7.2.json would work like https://endoflife.date/api/redis/7.2.json
for whatever versions there are of course
The problem/use-case that the feature addresses
A clear way to see when versions are being supported/are EOL online as well as a way to programmatically check using an API.
Description of the feature
eol.date provides both a web view as well as an API that lets anyone easily request current version/eol data for any product they are tracking. (See https://endoflife.date/redis or https://endoflife.date/api/redis.json for redis example).
Alternatives you've considered None that I found
Additional information
This basically boils down to a markdown file with YAML format and creating a PR to their repo. Here is the redis example: https://github.com/endoflife-date/endoflife.date/blob/master/products/redis.md?plain=1