Skip to content

[Snyk] Security upgrade hono from 4.7.6 to 4.10.3 #212

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

[Snyk] Security upgrade hono from 4.7.6 to 4.10.3 #212

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion apps/docs-autorag/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,7 +19,7 @@
"@repo/mcp-observability": "workspace:*",
"agents": "0.2.19",
"cloudflare": "4.2.0",
"hono": "4.7.6",
"hono": "4.10.3",
Copy link

@gemini-code-assist gemini-code-assist bot Nov 1, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

This PR correctly updates hono to a secure version. Consider using a caret (^) for the version range (e.g., ^4.10.3) to automatically receive future non-breaking security updates and bug fixes. While pinning versions ensures deterministic builds, it requires manual updates for every patch, which can delay fixing vulnerabilities. Since other dependencies are also pinned, this might be a deliberate project choice. If not, adopting caret versioning for dependencies could improve maintainability.

Suggested change
"hono": "4.10.3",
"hono": "^4.10.3",

"mime": "4.0.6",
"zod": "3.24.2"
},
Expand Down
Loading