Skip to content

fix(ci): pin supported Node security patch versions - #2772

Open
chaliy wants to merge 1 commit into
mainfrom
codex/security-node-builds-20261022
Open

chaliy wants to merge 1 commit into
mainfrom
codex/security-node-builds-20261022

Conversation

@chaliy

@chaliy chaliy commented Oct 22, 2026

Copy link
Copy Markdown
Contributor

What changed

Supported Node22/24 build, site and package-release recipe lanes select the October21 security patch versions22.23.4/24.22.1 instead of cached floating majors. Both native-binding runtime matrices use the same exact patched versions. The existing Windows/Node24 exception follows its updated exact matrix value.

Why

A floating major can reuse a runner-cached pre-fix runtime after a security release. Node runtime/OpenSSL/root-store fixes are separate from npm lockfile auditing.

Before / After

Node22→22.23.4 and24→24.22.1 for supported CI/build lanes. No interpreter/API behavior or dependency lock changes. The intentionally retained Node20 compatibility-only test lane is EOL and has no upstream supported security patch; it is not represented as fixed or as a deployment recommendation. Published native consumers still need the user's patched library artifacts and their own supported Node runtime.

Validation: full just pre-pr PASS on repository-pinned Rust1.95.0;7259 passed Rust test results across34 groups,65 existing ignored;179 Python script tests; format/strictClippy/docs/OKF/capability/workflow parity; cargo-vet success under unchanged policy. Actionlint structural validation and37 docs-route checks pass. Affected hosted JS/site CI must pass before merge. The initial check on workspaceRust1.99 was corrected to the repository pin without changing Rust source or lint policy.

Risk

  • Low: patch runtime selection; existing Node20 compatibility checks and Windows exception retain their meaning.
  • Release definitions are updated; release/manual triggers remain unchanged. No publish workflow is dispatched and no library/package release is created.

Remaining findings

Development-only braces3.0.3 remains via AVA/globby/micromatch; latest AVA8.1.0 still uses that graph and no patched braces version is published. Native TLS/Wasmtime fixes already landed separately. User-owned Rust/JS/Python publication and downstream lock refresh remain required.

Checklist

  • Existing tests and full pre-pr run
  • Backward compatibility considered
  • Final affected hosted CI green
  • All review comments addressed

@cloudflare-workers-and-pages

Copy link
Copy Markdown

Deploying with  Cloudflare Workers  Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status Name Latest Commit Preview URL Updated (UTC)
✅ Deployment successful!
View logs
bashkit 47ab411 Commit Preview URL

Branch Preview URL
Oct 22 2026, 03:10 PM

@chaliy
chaliy marked this pull request as ready for review October 22, 2026 15:39
@codecov

codecov Bot commented Oct 22, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

This branch has not been deployed

No deployments
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.

1 participant