nodejs.org icon indicating copy to clipboard operation
nodejs.org copied to clipboard

Link from releases.md to a machine-readable version

Open fulldecent opened this issue 5 years ago • 3 comments

Currently the page https://nodejs.org/en/about/releases/ provides a human-readable list of supported Node.js versions. That's great.

Please link directly from that page to a machine-readable version of the same information.


P.S. I am working on GitHub Actions for building Node.js projects. Having this information will be helpful for me because then GitHub Actions can stay up-to-date and support continuous integration workflows always including new supported versions of Node.js.


P.P.S. I hate projects that say "we require Node.js v10, it's still supported, and when enough people complain we'll start thinking about v11 [sic]"

fulldecent avatar Dec 23 '20 15:12 fulldecent

Hey @fulldecent, does this link fits your needs? https://nodejs.org/dist/index.json

rodion-arr avatar Dec 23 '20 16:12 rodion-arr

Thank you, this is related. But it does not show which releases are supported.

fulldecent avatar Dec 23 '20 18:12 fulldecent

The canonical source of truth for releases is the Release WG (https://github.com/nodejs/Release). A machine readable format can be found in https://github.com/nodejs/Release/blob/master/schedule.json and is what is used to build https://nodejs.org/en/about/releases/ (see https://github.com/nodejs/nodejs.org/blob/master/scripts/helpers/release-schedule.js).

I believe the Package Maintenance Group (https://github.com/nodejs/package-maintenance) were looking at things like tools/guidelines for CI such as GitHub Actions. https://github.com/pkgjs/nv, for example, provides a Node.js API.

richardlau avatar Dec 23 '20 21:12 richardlau

Closing as there are already machine readable formats.

ovflowd avatar Mar 12 '23 13:03 ovflowd