Skip to content

Unpin CI Node version from 22.22.2 to 22 - #2

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

  • ci.yml uses node-version: 22 instead of the exact 22.22.2 pin.

Why

The exact 22.22.2 pin predates the 2026-10-21 Node security releases (CVE-2026-111497, Brotli decoder OOB write, fixed in 22.23.4) and can never pick up a patch. A floating major pin resolves to the current patched 22.x, matching the rest of our CI.

CI-only change, no runtime code.


Note

Low Risk
CI-only workflow change with no application or runtime impact.

Overview
Updates the GitHub Actions CI workflow so actions/setup-node uses node-version: 22 instead of the exact 22.22.2 pin.

CI will resolve to the current patched 22.x on each run (including security fixes) rather than staying on an outdated patch that cannot auto-update.

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

The exact 22.22.2 pin predates the 2026-10-21 security releases
(CVE-2026-111497, Brotli decoder, fixed in 22.23.4). A floating major
pin resolves to patched releases automatically, matching the rest of
our CI.
@ulziibay-kernel
ulziibay-kernel marked this pull request as ready for review October 22, 2026 21:58
@ulziibay-kernel
ulziibay-kernel merged commit 1f0cdab into main Oct 22, 2026
1 check 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