Repository navigation
fix(security): standardize standalone runtimes on Node 24.22.1 - #6365
Merged
Merged
Conversation
Pin runtime images, CI and downloads to the October security release; preserve artifact verification and require patched Node 24 in standalone launchers. Update standalone Undici, add runtime baseline and Helm probe regression coverage, and document the separate rebuild/deployment and Electron follow-ups.
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub. 4 Skipped Deployments
|
…-october-21 # Conflicts: # docs/computer-use/workbot.md # evals/packages/open-workplace/README.md # evals/packages/open-workplace/package.json
OmarMcAdam
had a problem deploying
to
pr-internal-specs
October 22, 2026 16:47 — with 
GitHub Actions
Error
GitHub Actions
Error
Contributor
OpenWork evidence
Run details · Open the preview to inspect evidence and sandbox options. |
Deploying openwork with
|
| Latest commit: |
2874768
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://625d49e2.openwork.pages.dev |
| Branch Preview URL: | https://nodejs-security-stuffs-octob.openwork.pages.dev |
Contributor
Warden: needs a human approvalThis PR changes Warden itself, so Warden can't approve it. Changed: Reviewed |
Resolve the security review by replacing the mutable v6 action ref with its verified full commit SHA. Add a regression check that rejects mutable setup-node refs in the package-write workflow; retain Warden's human-approval safeguard.
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What is this about?
Standardize standalone OpenWork runtimes on Node.js 24.22.1 and update separately installed Undici security releases.
What problem does it solve?
Untrusted provider and MCP responses reach networking and decompression code affected by the October Node security advisories.
What was the situation before?
Server images used floating Node 22 tags, some sandboxes used Node 20 or older Node 24 patches, and installers accepted unsupported runtimes.
How is this implemented?
docs/node-runtime-security.md; Electron's embedded runtime remains separate.What else changed?
none.
Release note
Standalone server and bootstrap installations now require Node.js 24.x version 24.22.1 or newer; the bootstrap installer downloads a private supported runtime when needed.
Evidence
No E2E: this is a runtime/deployment update. Launcher and installer integration tests, rendered Helm-hook tests, and service builds cover the change.
scripts/tests/node-runtime-baseline.test.mjs— before: outdated runtime pins; after: consistent patched Node 24 pins and Undici releases.