Repository navigation
Patch security advisories in Node.js, NGINX, Angular and the server crates - #320
Merged
Merged
Conversation
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
This moves the web and server toolchains to releases that fix published advisories. Node.js goes to the 24.22.1 security release, NGINX is pinned to 1.31.8, Angular goes to 22.2.3, and the server crates are refreshed with
cargo update. Production web dependencies now report no advisories. Two stay because no fixed release exists:braces3.0.3, which only dev tooling pulls in, andh20.3, whichactix-http3 still requires and which is unreachable because NGINX talks HTTP/1.1 to the server.What changed
Sec-WebSocket-Key, sinceactix-http3.19 rejects keys that aren't base64 of 16 bytescargo updatefixes RUSTSEC-2026-0385 inctutilsand RUSTSEC-2026-0383 inwebpki-root-certs, and replaces the yankedyoke-derive0.8.3.nvmrc, CI and both Dockerfile stages@angular/routerand@angular/platform-server, and@angular/cli22.2.4 brings@modelcontextprotocol/server2.3.1overridesentry forcesvite8.3.5 under@angular/build, which still pins the vulnerable 8.3.0follow-redirectsandlaunch-editormove to their patched releasespackage.jsonminimums raised to match1.31.8-alpine-slim, sincedocker compose builddoesn't re-pull a floating tag