Skip to content

Bump release-please Node version to 22 - #209

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

  • release-please.yml uses node-version: '22' instead of the exact '18.20.2' pin.

Why

Node 18 is EOL and receives no security fixes — including the 2026-10-21 Brotli decoder fix (CVE-2026-111497). An exact 18.20.2 pin can never pick up a patch; the floating '22' pin resolves to the current patched 22.x.

CI-only change, no runtime code.


Note

Low Risk
Single CI setup-node version bump with no application or release logic changes.

Overview
Updates the Release Please GitHub Actions workflow to run on Node 22 (node-version: '22') instead of the pinned 18.20.2, aligning this job with other workflows that already use Node 22.

This is CI-only (setup for building/running the pinned release-please tooling); it does not change SDK runtime code. The floating 22 pin lets the runner pick up current 22.x patches rather than staying on an EOL Node 18 line.

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

Node 18 is end-of-life and receives no security fixes, including the
2026-10-21 Brotli decoder fix (CVE-2026-111497). The exact 18.20.2 pin
can never be patched; use 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 b9653c8 into main Oct 22, 2026
12 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