Skip to content

ci: pin Node.js security releases in build workflows - #111

Merged
kkdev92 merged 1 commit into
mainfrom
chore/node-security-20261021
Oct 22, 2026
Merged

kkdev92 merged 1 commit into
mainfrom
chore/node-security-20261021

Conversation

@kkdev92

@kkdev92 kkdev92 commented Oct 21, 2026

Copy link
Copy Markdown
Owner

Pins the CI matrix to Node.js 22.23.4, 24.22.1 and 26.12.1, and uses 26.12.1 for packaging, contract, documentation and release jobs.

Why

The explicit versions select the security releases instead of an older runtime matching a major-only selector.

What changed

Resolve each existing matrix entry to its patched version while retaining the matrix labels used by required checks. Pin the remaining Node.js jobs to 26.12.1.

Verification

  • On Node.js 26.12.1: npm ci, npm run quality and npm run verify:package passed.
  • Parsed the workflow YAML and checked that matrix values, job names, triggers and permissions are preserved.
  • The 22.x and 24.x matrix entries are covered by CI; the local gate used 26.12.1.

🤖 Generated with Codex

Select patched Node.js versions explicitly so cached runtimes cannot
precede the security fixes.

Node.js versions: 22.23.4, 24.22.1, 26.12.1.

Validation: configuration parsing and git diff --check.

Co-Authored-By: Codex <noreply@openai.com>
@kkdev92
kkdev92 merged commit 380ebd4 into main Oct 22, 2026
10 checks passed
@kkdev92
kkdev92 deleted the chore/node-security-20261021 branch October 22, 2026 00:24
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