History

GUARDiA AutoDeploy 91a573c504 feat(icons): Manager 라인 SVG 아이콘 적용 + 테스트 결과 [auto-sync]		2026-06-03 20:10:24 +09:00
..
data	feat(icons): Manager 라인 SVG 아이콘 적용 + 테스트 결과 [auto-sync]	2026-06-03 20:10:24 +09:00
LICENSE	feat(icons): Manager 라인 SVG 아이콘 적용 + 테스트 결과 [auto-sync]	2026-06-03 20:10:24 +09:00
package.json	feat(icons): Manager 라인 SVG 아이콘 적용 + 테스트 결과 [auto-sync]	2026-06-03 20:10:24 +09:00
README.md	feat(icons): Manager 라인 SVG 아이콘 적용 + 테스트 결과 [auto-sync]	2026-06-03 20:10:24 +09:00

README.md

Node.js releases data

All data is located in data directory.

data/processed contains envs.json with node.js releases data preprocessed to be used by Browserslist and other projects. Each version in this file contains only necessary info: version, release date, LTS flag/name, and security flag.

data/release-schedule contains release-schedule.json with node.js releases date and end of life date.

Installation

npm install node-releases

Usage

// CommonJS
const envs = require('node-releases/data/processed/envs.json');
const schedule = require('node-releases/data/release-schedule/release-schedule.json');

// ESM (Node.js 22+)
import envs from 'node-releases/data/processed/envs.json' with { type: 'json' };
import schedule from 'node-releases/data/release-schedule/release-schedule.json' with { type: 'json' };

Releases

Releases are published automatically by a nightly GitHub Actions workflow whenever upstream Node.js release data changes. Publishing uses npm trusted publishing (OIDC, no long-lived tokens) and ships provenance attestations.