chore(deps): bump hono from 4.12.26 to 4.12.27 in /packages/treeshake-server - #4929
Conversation
Bumps [hono](https://github.com/honojs/hono) from 4.12.26 to 4.12.27. - [Release notes](https://github.com/honojs/hono/releases) - [Commits](honojs/hono@v4.12.26...v4.12.27) --- updated-dependencies: - dependency-name: hono dependency-version: 4.12.27 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
|
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: bdc4b19a8d
ℹ️ 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.26", | ||
| "hono": "4.12.27", |
There was a problem hiding this comment.
Commit the matching pnpm lockfile update
This manifest now asks for hono 4.12.27, but pnpm-lock.yaml still records the packages/treeshake-server importer specifier and resolved version as 4.12.26, so the frozen installs used by .github/workflows/build-and-test.yml:39-40 and .github/workflows/e2e-treeshake.yml:32-33 will reject the checkout before any tests run; the pnpm install docs state that CI installs fail when the lockfile needs an update. Please commit the regenerated lockfile with this bump.
Useful? React with 👍 / 👎.
Bumps hono from 4.12.26 to 4.12.27.
Release notes
Sourced from hono's releases.
Commits
97c6fe14.12.27aa92177Merge commit from forkcd3f6f7Merge commit from forkd4853a8fix(jsx): make merged context-isolation tests pass tsc type check (#5037)6735feafix(jsx): cast awaitedFallback through unknown to fix Deno type check (#5036)fab3b13Merge commit from fork9f0dadfci: use npm Staged publishing (#5035)Dependabot 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.