Repository navigation
Patch Hono and container vulnerabilities and harden markup conversion - #191
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 both dependency lockfiles contain vulnerable Hono packages. Upgrade Hono to 4.13.18 and @hono/node-server to 2.1.8 in the API and migration tool, move both container builders to Node 26.13.1, and require patched zlib at image build time. Explicitly retain the existing hardened tc-core-library-js v4.0.0-rc.2 for linked service dependencies so lockfile regeneration cannot restore its older JWT verifier.
Code scanning alert #616 identifies empty inline-element replacements in the historical Marathon description converter. Preserve a separator for empty inline elements, as already done for block elements, so removal cannot join surrounding markup fragments. Add eight cases covering the supported inline elements while retaining the final deterministic tag scanner.
Validation:
Merge and the normal image rollout are required to replace the vulnerable deployed digest.