Skip to content

Bump CI Node version to 22 - #8

Merged
ulziibay-kernel merged 1 commit into
mainfrom
hypeship/bump-ci-node-22
Oct 22, 2026
Merged

ulziibay-kernel merged 1 commit into
mainfrom
hypeship/bump-ci-node-22

Conversation

@ulziibay-kernel

@ulziibay-kernel ulziibay-kernel commented Oct 22, 2026 •

Copy link
Copy Markdown
Contributor

Summary

  • npm-publish.yml and publish.yml use node-version: '22' instead of '20'.

Why

Node 20 is EOL and receives no security fixes — including the 2026-10-21 Brotli decoder fix (CVE-2026-111497). The floating '22' pin resolves to the current patched 22.x.

CI-only change, no runtime code.


Note

Low Risk
CI workflow configuration only; no application runtime or dependency changes.

Overview
Updates the Node.js version used in GitHub Actions from 20 to 22 in the NPM publish and version-bump workflows (npm-publish.yml, publish.yml).

This is CI-only—the setup-node step for lint, build, and npm publish now runs on the current 22.x line instead of EOL Node 20.

Reviewed by Cursor Bugbot for commit a02b512. Bugbot is set up for automated code reviews on this repo. Configure here.

Node 20 is end-of-life and receives no security fixes, including the
2026-10-21 Brotli decoder fix (CVE-2026-111497). Pin the major to the
supported 22 line, which resolves to patched releases.
@ulziibay-kernel
ulziibay-kernel marked this pull request as ready for review October 22, 2026 21:58
@ulziibay-kernel
ulziibay-kernel merged commit 8819a79 into main Oct 22, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants