Skip to content

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

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 #199

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/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.7",
"cloudflare": "4.2.0",
"hono": "4.7.6",
"hono": "4.10.3",
Copy link

@gemini-code-assist gemini-code-assist bot Oct 31, 2025

Choose a reason for hiding this comment

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

medium

While this PR correctly updates hono to a secure version, the project is pinning dependencies to exact versions. This practice ensures reproducible builds, but it also prevents automatic updates for minor and patch releases, which often include important security fixes and bug fixes. This means you have to wait for a manual update or a bot like Snyk to create a PR.

Consider using a caret (^) for versioning to allow for non-breaking updates. This would automatically pull in future patches and minor releases within the same major version, improving security and maintainability. For example, using ^4.10.3 would match any version from 4.10.3 up to (but not including) 5.0.0.

This change would help in keeping dependencies up-to-date more easily. You might consider applying this strategy to other dependencies in this file as well for consistency.

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

"zod": "3.24.2"
},
"devDependencies": {
Expand Down
Loading