zio/zioinfo-mail
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
cfe2901a55
zioinfo-mail/workspace/guardia-manager/frontend/node_modules/node-releases
History
DESKTOP-TKLFCPR\ython cfe2901a55 refactor(structure): consolidate all projects under workspace/ 
- itsm/    -> workspace/guardia-itsm/
- manager/ -> workspace/guardia-manager/
- app/     -> workspace/guardia-messenger/
- manual/  -> workspace/guardia-docs/

workspace/zioinfo-web/ unchanged.
git mv preserves full commit history.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
2026-05-31 23:50:56 +09:00
..
data refactor(structure): consolidate all projects under workspace/ 2026-05-31 23:50:56 +09:00
LICENSE refactor(structure): consolidate all projects under workspace/ 2026-05-31 23:50:56 +09:00
package.json refactor(structure): consolidate all projects under workspace/ 2026-05-31 23:50:56 +09:00
README.md refactor(structure): consolidate all projects under workspace/ 2026-05-31 23:50:56 +09:00

README.md

Node.js releases data

npm version License: MIT

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.