chore: updated node to supported 22,24,25 (#7628)

* chore: updated node to supported 22,24,25

* chore: updated node to supported 22,24,25

* chore: updated node to supported 22,24,25

* chore: updated node to supported 22,24,25

* chore: upgrade deb

* chore: upgrade dockerfile

* chore: use explicit node

* chore: use node 22

* chore: use node 22
This commit is contained in:
SamTV12345 2026-04-28 22:45:28 +02:00 committed by GitHub
parent 421869daec
commit c55007361c
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
23 changed files with 129 additions and 45 deletions

View file

@ -85,10 +85,9 @@ If a package previously had an `NPM_TOKEN` secret in CI:
## Requirements
- **Node.js**: >= 20.17.0 on the runner. npm 11 requires
`^20.17.0 || >=22.9.0`. The npm docs nominally recommend Node 22.14+, but
Node 20.17+ works fine — the project's `engines.node` already requires
`>=20.0.0`, and `setup-node@v6 with version: 20` resolves to the latest 20.x.
- **Node.js**: >= 22 on the runner. npm 11 requires `>=22.9.0`, which
`setup-node@v6 with version: 22` satisfies (resolves to the latest 22.x).
The project's `engines.node` requires `>=22.0.0`.
- **npm CLI**: >= 11.5.1. The publish workflow runs `npm install -g npm@latest`
before publishing so the bundled npm version doesn't matter.
- **Runner**: must be a GitHub-hosted (cloud) runner. Self-hosted runners are