Repository navigation
Patch Hono and refresh the secure Node runtime - #179
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.
The deployed image and Dependabot report vulnerable Hono middleware and HTTP-server dependencies. Upgrade Hono to 4.13.18 and @hono/node-server to 2.1.8, update the build Node version to 26.13.1, and refresh the digest-pinned Chainguard runtime to the patched Node release. Preserve the existing non-root runtime and Prisma/OpenSSL compatibility checks.
Validation: full Docker build passes frozen installation, dependency compatibility tests, lint, compilation, and the final-image Prisma migration-engine check. The rebuilt image has zero critical/high/medium Trivy vulnerability findings, including unfixed findings. pnpm audit reports zero critical/high/moderate vulnerabilities (two low). Runtime uses Node 26.13.1 and UID 65532.
Merge and the normal image rollout are required to replace the vulnerable deployed digest.