Repository navigation
Conversation
Picks up fixes for CVE-2026-111497 (Brotli OOB write), TLS hostname verification bypasses, and undici/OpenSSL/c-ares updates. Co-Authored-By: Claude <noreply@anthropic.com>
hyoban
requested review from
GareArc,
QuantumGhost,
crazywoola,
iamjoel,
laipz8200 and
lyzno1
as code owners
October 22, 2026 01:15
hjlarry
approved these changes
Oct 22, 2026
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #44515 +/- ##
==========================================
- Coverage 88.92% 88.91% -0.01%
==========================================
Files 5572 5572
Lines 333940 333940
Branches 66834 66834
==========================================
- Hits 296941 296935 -6
- Misses 31835 31841 +6
Partials 5164 5164
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
Member
Author
|
Closing as a duplicate of #44511, which makes the same Node.js 24.22.1 bump and was opened first. |
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.
Summary
Bump Node.js from 24.20.0 / 24.21.0 to 24.22.1, the 24.x release in the October 2026 Node.js security releases.
Relevant fixes for us:
dns.resolveNUL truncation, keep-alive response desync.Changes:
devEnginesruntime andengines.node(^24.22.1) in root,cli,packages/dev-proxy,packages/image-resources;devEnginesinsdks/nodejs-client(its>=18engines range is unchanged).web/Dockerfile(node:24.22.1-alpine),api/Dockerfile(NodeSource24.22.1-1nodesource1),dify-agent-runtime/docker/Dockerfile,.devcontainer/devcontainer.json.pnpm-lock.yamlregenerated; only the Node runtime entries changed.Verified that the nodejs.org binaries, Docker Hub
node:24.22.1-alpine, and NodeSource24.22.1-1nodesource1(amd64/arm64) are all published. Docker images were not built locally.Checklist
make lint && make type-check(backend) andvp staged(frontend) to appease the lint godsPre-commit
vp staged(eslint + vp fmt) passed; backend lint/type-check not run since only the Dockerfile changed on the API side.From Claude Code