Repository navigation
Require patched Node runtimes for October security fixes - #14
Merged
Merged
Conversation
Deploying patchling with
|
| Latest commit: |
2124c01
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://447c872f.patchling.pages.dev |
| Branch Preview URL: | https://security-october-2026-node-r.patchling.pages.dev |
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.
The published runtime requirement and CI allowed Node 20 and pre-fix Node releases. Require patched Node 22.23.4, 24.22.1, or 26.12.1 and run CI against the fixed supported branches. Local development selects 24.22.1. This addresses the Brotli decoder memory corruption plus the TLS/HTTP/DNS and CA updates in the official October Node advisory.
Validation: existing offline test suite passed on a separately downloaded Node 24.22.1, verified against the official SHASUMS256.txt. CI tests the configured fixed branches. No live API spend.
This changes repository requirements and CI; it does not update already installed npm packages or running services. Consumers must update their Node executable and restart applications. Rollback: revert this commit; retain a patched Node runtime.