zioinfo-mail/app/node_modules/node-releases
DESKTOP-TKLFCPR\ython 11c670f2a0 refactor: 101.79.17.164 → zioinfo.co.kr 전체 도메인 변환 + Manager UI 배포
- 37개 파일 IP → zioinfo.co.kr 치환 (소스/매뉴얼/설정/하네스)
- Manager DrConsole/NetworkConsole/CsapConsole 빌드 + /var/www/manager/ 배포
- 테스트: Manager HTTP 200, ITSM 신규 API 7개 전체 200

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
2026-05-31 10:09:17 +09:00
..
data refactor: 101.79.17.164 → zioinfo.co.kr 전체 도메인 변환 + Manager UI 배포 2026-05-31 10:09:17 +09:00
LICENSE refactor: 101.79.17.164 → zioinfo.co.kr 전체 도메인 변환 + Manager UI 배포 2026-05-31 10:09:17 +09:00
package.json refactor: 101.79.17.164 → zioinfo.co.kr 전체 도메인 변환 + Manager UI 배포 2026-05-31 10:09:17 +09:00
README.md refactor: 101.79.17.164 → zioinfo.co.kr 전체 도메인 변환 + Manager UI 배포 2026-05-31 10:09:17 +09:00

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.