Repository navigation
fix(deps): take the patched hono release - #173
Merged
Merged
Conversation
GHSA-4m76-xfj5-7975, GHSA-h7mg-cq63-vhpq and GHSA-3gg2-335m-rxc6 were published against hono 4.13.15 and older, which the MCP SDK and @hono/node-server resolved to 4.13.13. Their ranges already admit the fix, so only the lockfile moves, to 4.13.17: 4.13.18 is still inside the release cooldown.
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.
What
Moves the transitive
honofrom 4.13.13 to 4.13.17 inpnpm-lock.yaml. Nothing else changes.Why
check:securityfails on the release pull request #172 since GHSA-4m76-xfj5-7975, GHSA-h7mg-cq63-vhpq and GHSA-3gg2-335m-rxc6 were published against hono 4.13.15 and older. The MCP SDK (^4.11.4) and@hono/node-server(^4 || ^5.0.0-0) already admit the fix, so only the lockfile moves. 4.13.18 is still inside the three-day release cooldown.This goes straight to
mainso #172 can release;devtakes it with the next back-merge frommain.Verification
pnpm install --frozen-lockfileis clean.pnpm check:securitypasses: the four remaining advisories all have current path-specific reviews.