chore(deps): bump hono from 4.5.11 to 4.6.1 in the npm_and_yarn group across 1 directory

[dependabot]

Bumps the npm_and_yarn group with 1 update in the / directory: hono.

Updates hono from 4.5.11 to 4.6.1

Release notes

Sourced from hono's releases.

v4.6.1

What's Changed

• fix(build): improve addExtension esbuild plugin by @​kt3k in honojs/hono#3405

New Contributors

• @​kt3k made their first contribution in honojs/hono#3405

Full Changelog: honojs/hono@v4.6.0...v4.6.1

v4.6.0

Hono v4.6.0 is now available!

One of the highlights of this release is the Context Storage Middleware. Let's introduce it.

Context Storage Middleware

Many users may have been waiting for this feature. The Context Storage Middleware uses AsyncLocalStorage to allow handling of the current Context object even outside of handlers.

For example, let’s define a Hono app with a variable message: string.

type Env = {
  Variables: {
    message: string
  }
}
const app = new Hono<Env>()

To enable Context Storage Middleware, register contextStorage() as middleware at the top and set the message value.

import { contextStorage } from 'hono/context-storage'
//...
app.use(contextStorage())
app.use(async (c, next) => {
c.set('message', 'Hello!')
await next()
})

getContext() returns the current Context object, allowing you to get the value of the message variable outside the handler.

import { getContext } from 'hono/context-storage'
</tr></table>

... (truncated)

Commits

• e0d17a3 v4.6.1
• 85c7dc6 fix(build): improve addExtension esbuild plugin (#3405)
• 73ff6c0 v4.6.0
• 2da003b Merge pull request #3394 from honojs/next
• 743f66c fix(bearer-auth): typo (#3404)
• c240ea5 feat(bearer-auth): added custom response message options (#3372)
• c50be25 feat(basic-auth): added custom response message option (#3371)
• a86f3ce feat(serve-static): add onFound option (#3396)
• 3c4d4c2 fix(secure-headers): optimize getPermissionsPolicyDirectives function (#3398)
• c2b0de4 feat(context): make fetch Response headers mutable (#3318)
• Additional commits viewable in compare view

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 rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions
  You can disable automated security fix PRs for this repo from the Security Alerts page.