[Snyk] Security upgrade hono from 4.12.14 to 4.12.16 - #173
Conversation
The following vulnerabilities are fixed with an upgrade: - https://snyk.io/vuln/SNYK-JS-HONO-16438966 - https://snyk.io/vuln/SNYK-JS-HONO-16438965
|
Important Review skippedIgnore keyword(s) in the title. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: e91e8a9092
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| "dependencies": { | ||
| "@modelcontextprotocol/sdk": "^1.26.0", | ||
| "hono": "^4.12.14", | ||
| "hono": "^4.12.16", |
There was a problem hiding this comment.
Regenerate lockfile for hono upgrade
Bumping hono in platforms/mcp/package.json without updating pnpm-lock.yaml leaves the workspace lock pinned to hono 4.12.14 in the platforms/mcp importer, so the vulnerable version is still what gets installed in lockfile-driven environments. This also risks CI failures because repository workflows install with pnpm install --frozen-lockfile (checked in .github/workflows/ci.yml lines 66, 232, 322, and 428), which requires the lockfile to match manifest changes.
Useful? React with 👍 / 👎.
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
|
Closing as superseded by current main. While resolving this PR, origin/main already contains a newer patched MCP hono version (platforms/mcp/package.json uses ) and matching pnpm-lock.yaml entries (). Branch-diff proof from the rebase checkout showed and , so this PR has no remaining unique change to land. |
Snyk has created this PR to fix 2 vulnerabilities in the pnpm dependencies of this project.
Snyk changed the following file(s):
platforms/mcp/package.jsonVulnerabilities that will be fixed with an upgrade:
SNYK-JS-HONO-16438966
SNYK-JS-HONO-16438965
Important
Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic
Learn how to fix vulnerabilities with free interactive lessons:
🦉 Allocation of Resources Without Limits or Throttling