Repository navigation
Bump Node pins for the 2026-11-11 security releases - #911
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
kvz
marked this pull request as ready for review
November 11, 2026 22:28
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.
Node.js published security releases on 2026-11-11: 16 CVEs (7 high, 6 medium, 3 low), almost all in Node's own HTTP/2 and TLS servers, with updated bundled llhttp and undici. The fixed versions are 26.13.1, 24.22.3 and 22.23.5, and the release notes list no breaking changes. This moves this repository's exact Node pins to the fixed patch of their line.
What changes
ci.ymlandrelease.yml:node-version26.12.1 → 26.13.1.github/contributing.md: the Node version it names for Changesets commandsNot changed:
tests.ymlstill runs onnode-version: 20.x. That is a floating range on Node 20, which is end-of-life and gets no fix for these CVEs; moving it is a support-policy decision, not a pin bump, so it is left for a separate change.Version pins only; CI exercises the new versions. No changeset: no published code changes.
🤖 Claimed by kvz on
framework1/tus-node-serversince 2026-11-11 · resume:claude --resume 7b680034-4a27-47aa-b2e8-812993e1a2f1