Brunobkr/llama.cpp_AlgMor24_github

1# Node.js releases data2 3[![npm version](https://img.shields.io/npm/v/node-releases.svg)](https://www.npmjs.com/package/node-releases)4[![License: MIT](https://img.shields.io/npm/l/node-releases.svg)](./LICENSE)5 6All data is located in `data` directory.7 8`data/processed` contains `envs.json` with node.js releases data preprocessed to be used by [Browserslist](https://github.com/ai/browserslist) and other projects. Each version in this file contains only necessary info: version, release date, LTS flag/name, and security flag.9 10`data/release-schedule` contains `release-schedule.json` with node.js releases date and end of life date.11 12## Installation13 14```bash15npm install node-releases16```17 18## Usage19 20```js21// CommonJS22const envs = require('node-releases/data/processed/envs.json');23const schedule = require('node-releases/data/release-schedule/release-schedule.json');24 25// ESM (Node.js 22+)26import envs from 'node-releases/data/processed/envs.json' with { type: 'json' };27import schedule from 'node-releases/data/release-schedule/release-schedule.json' with { type: 'json' };28```29 30## Releases31 32Releases are published automatically by a nightly GitHub Actions workflow whenever upstream Node.js release data changes. Publishing uses [npm trusted publishing](https://docs.npmjs.com/trusted-publishers) (OIDC, no long-lived tokens) and ships [provenance attestations](https://docs.npmjs.com/generating-provenance-statements).33