Skip to content

chore(deps): bump hono from 4.12.7 to 4.12.12 in /packages/treeshake-server #4638

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

Closed
dependabot wants to merge 1 commit into from
Closed

chore(deps): bump hono from 4.12.7 to 4.12.12 in /packages/treeshake-server #4638

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 packages/treeshake-server/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -35,7 +35,7 @@
"@hono/node-server": "1.19.10",
"@hono/zod-validator": "0.7.4",
"dotenv": "16.4.5",
"hono": "4.12.7",
"hono": "4.12.12",
Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot Apr 8, 2026

Choose a reason for hiding this comment

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

P1 Badge Update lockfile to include the new hono version

Bumping hono in packages/treeshake-server/package.json without updating pnpm-lock.yaml leaves the workspace inconsistent: the lockfile still resolves this importer through hono@4.12.7 (including the @hono/node-server/@hono/zod-validator edges), so deterministic installs continue using the old vulnerable version and CI jobs that run pnpm install --frozen-lockfile will fail until the lockfile is regenerated.

Useful? React with 👍 / 👎.

"json-stable-stringify": "1.3.0",
"nanoid": "5.1.6",
"p-limit": "7.2.0",
Expand Down
Loading