chore(deps): bump hono from 4.12.7 to 4.12.16 in /packages/treeshake-server#4713
chore(deps): bump hono from 4.12.7 to 4.12.16 in /packages/treeshake-server#4713dependabot[bot] wants to merge 1 commit intomainfrom
Conversation
Bumps [hono](https://github.com/honojs/hono) from 4.12.7 to 4.12.16. - [Release notes](https://github.com/honojs/hono/releases) - [Commits](honojs/hono@v4.12.7...v4.12.16) --- updated-dependencies: - dependency-name: hono dependency-version: 4.12.16 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
|
❌ Deploy Preview for module-federation-docs failed. Why did it fail? →
|
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 3c0927ffee
ℹ️ About Codex in GitHub
Codex has been enabled to automatically 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 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| "@hono/zod-validator": "0.7.4", | ||
| "dotenv": "16.4.5", | ||
| "hono": "4.12.7", | ||
| "hono": "4.12.16", |
There was a problem hiding this comment.
Update the lockfile with the Hono bump
Because this changes the package manifest without updating pnpm-lock.yaml, the workspace lockfile still records packages/treeshake-server with hono specifier/version 4.12.7 and peer resolutions against hono@4.12.7. Any CI or developer setup that runs pnpm install --frozen-lockfile for this repo will reject the out-of-sync lockfile before tests/builds can run, so the dependency bump will not be installable until the lockfile is regenerated and committed.
Useful? React with 👍 / 👎.
|
Superseded by #4720. |
Bumps hono from 4.12.7 to 4.12.16.
Release notes
Sourced from hono's releases.
... (truncated)
Commits
90d41824.12.16db05b96Merge commit from fork614b834Merge commit from fork027e3dffix(method-override): handle Content-Type with charset parameter (#4894)f774f8d4.12.1518fe604fix(jwt): support single-line PEM keys (#4889)cf2d2b74.12.1466daa2eMerge commit from forkfa2c74ffix(aws-lambda): handle invalid header names in request processing (#4883)37799274.12.13Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)You can disable automated security fix PRs for this repo from the Security Alerts page.