Repository navigation
chore: pin node 24.22.1 for the eMadhra TLS vulnerability - #250
Merged
Merged
Conversation
- Dockerfile: node:24-alpine -> node:24.22.1-alpine - CI node 20.x -> 24.x; checkout v4->v7, setup-node v4->v7, docker/login v3->v4, build-push v6->v7 - engines.node ">= 20.0.0" -> ">= 24.22.1" in package.json and package-lock.json root entry Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
Dockerfile base image pinned to node:24.22.1-alpine (first Node 24 release with the TLS fix).
CI node 20.x -> 24.x; checkout v4->v7, setup-node v4->v7, docker/login v3->v4, build-push v6->v7.
engines.node set to >= 24.22.1.
Local verification: npm run jslint passes (0 errors); docker build OK, node -v in image prints v24.22.1, loading package.json OK.
🤖 Generated with Claude Code