Skip to content

ci(SEC-104): pin Node in package.json devEngines instead of .nvmrc - #406

Merged
glebedel merged 3 commits into
mainfrom
s2d2/sec-104-devengines-pin
Nov 11, 2026
Merged

glebedel merged 3 commits into
mainfrom
s2d2/sec-104-devengines-pin

Conversation

@glebedel

Copy link
Copy Markdown
Contributor

What

  • Moves the exact Node pin (22.23.4) from .nvmrc to package.json devEngines.runtime and deletes .nvmrc.
  • Workflows now read it with node-version-file: package.json. setup-node v6.3 and later read devEngines.runtime before engines.node, so CI gets the exact version, not the newest match of the engines range.
  • Bumps actions/setup-node to v6.5.0 (pinned SHA) where it was on v4 or v5: those versions do not read devEngines and would fall back to engines.node or fail.
  • onFail: "warn": npm warns on a mismatch instead of failing, so a local Node that is a patch behind is flagged without blocking work. CI stays exact through setup-node.

Why

One place for the Node version, read by CI and by the package manager. .nvmrc is only read by nvm and setup-node, and an engines range alone would let CI float to whatever release is newest. Docker base images are pinned separately and are unchanged.

Local verification

hub-docs node=v22.23.4 pm=npm install=0

Refs SEC-104. Requested by guillaume@stackone.com in Slack.

🤖 Generated with Claude Code

One source per repo: devEngines.runtime 22.23.4 (onFail: warn) is read by
setup-node (node-version-file: package.json) in CI.

Refs SEC-104.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Copilot AI balanced review requested due to automatic review settings October 30, 2026 18:47
@glebedel glebedel self-assigned this Oct 30, 2026
@mintlify

mintlify Bot commented Oct 30, 2026 •

Copy link
Copy Markdown
Contributor

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated
stackone-hub 🟢 Ready View Preview Nov 11, 2026, 6:25 PM

💡 Tip: Enable Automations to automatically generate PRs for you.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot was unable to review this pull request because the user who requested the review has insufficient remaining quota.

An organization owner can choose the repository organization as the billing source for reviews requested by members with a paid Copilot license. Learn about Copilot code review billing. Review the Copilot code review billing settings.

Keeps this branch from reintroducing a pre-fix Node when it merges.
https://nodejs.org/en/blog/vulnerability/november-2026-security-releases

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

@glebedel glebedel left a comment

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Review at head d9d391f4 (Node Nov 2026 security release, SEC-104).

  • Correctness (Codex pass over all 68 bump PRs): OK. Pins in this repo agree; no stale 22.23.4 / 24.22.1-2 / 26.12-13.0 left in the diff.
  • Security (Codex security-only pass): no findings. Lockfile node runtime URLs and hashes match the official SHASUMS256; no workflow permission or action-pin changes.
  • CI: all 1 checks green on this head.
  • Open review threads: 0.

Ready to merge from my side. GitHub approval still has to come from a person: s2d2 cannot approve PRs, and in this repo s2d2 acts with the same identity that opened the PR.

Requested by guillaume@stackone.com in Slack (#C05LDDNTJKV thread 1793813777.685889).

Resolves the .nvmrc conflict with the Nov 2026 Node bump: the pin lives in
package.json devEngines.runtime on this branch, so .nvmrc stays deleted.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@glebedel
glebedel merged commit 7812b3a into main Nov 11, 2026
1 check passed

This branch was successfully deployed

1 active deployment
staging — 754a2090 Deployed Nov 11, 2026 by mintlify[bot]
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.

3 participants