Skip to content

[Snyk] Upgrade hono from 4.8.8 to 4.9.8 #93

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

Jump to bottom
Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

[Snyk] Upgrade hono from 4.8.8 to 4.9.8 #93

wants to merge 1 commit into from

Conversation

@rnmeow
Copy link
Owner

@rnmeow rnmeow commented Oct 13, 2025

snyk-top-banner

Snyk has created this PR to upgrade hono from 4.8.8 to 4.9.8.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

  • The recommended version is 13 versions ahead of your current version.

  • The recommended version was released 25 days ago.

Release notes
Package name: hono
  • 4.9.8 - 2025-09-18

    What's Changed

    New Contributors

    Full Changelog: v4.9.7...v4.9.8

  • 4.9.7 - 2025-09-12

    Security

    • Fixed an issue in the bodyLimit middleware where the body size limit could be bypassed when both Content-Length and Transfer-Encoding headers were present. If you are using this middleware, please update immediately. Security Advisory

    What's Changed

    • fix(client): Fix parseResponse not parsing json in react native by @ lr0pb in #4399
    • chore: add .tool-versions file by @ 3w36zj6 in #4397
    • chore: update bun install commands to use --frozen-lockfile by @ 3w36zj6 in #4398
    • test(jwk): Add tests of JWK token verification by @ buckett in #4402

    New Contributors

    Full Changelog: v4.9.6...v4.9.7

  • 4.9.6 - 2025-09-03

    Security

    Fixed a bug in URL path parsing (getPath) that could cause path confusion under malformed requests.

    If you rely on reverse proxies (e.g. Nginx) for ACLs or restrict access to endpoints like /admin, please update immediately.

    See advisory for details: GHSA-9hp6-4448-45g2

    What's Changed

    Full Changelog: v4.9.5...v4.9.6

  • 4.9.5 - 2025-08-29

    What's Changed

    • chore: replace supertest with undici by @ BarryThePenguin in #4365
    • fix(aws-lambda): preserve percent-encoded values in query strings by @ yusukebe in #4372
    • feat(cors): Allow async functions for origin and allowMethods by @ jobrk in #4373
    • feat(cors): Correct origin function return type asynchronously returning null or undefined for origin by @ jobrk in #4375
    • fix(service-worker): correct args for app.fetch in handle by @ yusukebe in #4374
    • fix(language-detector): Detect language from path after getPath changed by @ iflamed in #4369

    New Contributors

    Full Changelog: v4.9.4...v4.9.5

  • 4.9.4 - 2025-08-22

    What's Changed

    Full Changelog: v4.9.3...v4.9.4

  • 4.9.3 - 2025-08-22

    What's Changed

    Full Changelog: v4.9.2...v4.9.3

  • 4.9.2 - 2025-08-15

    What's Changed

    • fix(jsx): 'plaintext-only' value for contenteditable attribute by @ object1037 in #4349
    • fix(client): handle query parameters in removeIndexString by @ yusukebe in #4352

    New Contributors

    Full Changelog: v4.9.1...v4.9.2

  • 4.9.1 - 2025-08-12

    What's Changed

    • feat(parseResponse): set DetailedError.name (+ error tests) by @ NamesMT in #4344
    • fix(parseResponse): should not include error responses in result by @ NamesMT in #4348

    Full Changelog: v4.9.0...v4.9.1

  • 4.9.0 - 2025-08-07

    Release Notes

    Hono v4.9.0 is now available!

    This release introduces several enhancements and utilities.

    The main highlight is the new parseResponse utility that makes it easier to work with RPC client responses.

    parseResponse Utility

    The new parseResponse utility provides a convenient way to parse responses from Hono RPC clients (hc). It automatically handles different response formats and throws structured errors for failed requests.

    import { parseResponse, DetailedError } from 'hono/client'

    // result contains the parsed response body (automatically parsed based on Content-Type)
    const result = await parseResponse(client.hello.$get()).catch(
    // parseResponse automatically throws an error if response is not ok
    (e: DetailedError) => {
    console.error(e)
    }
    )

    This makes working with RPC client responses much more straightforward and type-safe.

    Thanks @ NamesMT!

    New features

    • feat(bun): allow importing upgradeWebSocket and websocket directly #4242
    • feat(aws-lambda): specify content-type as binary #4250
    • feat(jwt): add validation for the issuer (iss) claim #4253
    • feat(jwk): add headerName to JWK middleware #4279
    • feat(cookie): add generateCookie and generateSignedCookie helpers #4285
    • feat(serve-static): use join to correct path resolution #4291
    • feat(jwt): expose utility function verifyWithJwks for external use #4302
    • feat: add parseResponse util to smartly parse hc's Response #4314
    • feat(ssg): mark old hook options as deprecated #4331

    All changes

    New Contributors

    Full Changelog: v4.8.12...v4.9.0

  • 4.8.12 - 2025-08-02

    What's Changed

    Full Changelog: v4.8.11...v4.8.12

  • 4.8.11 - 2025-08-01
  • 4.8.10 - 2025-07-29
  • 4.8.9 - 2025-07-26
  • 4.8.8 - 2025-07-25
from hono GitHub release notes

Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

@snyk-bot
fix: upgrade hono from 4.8.8 to 4.9.8
5920f3c 
Snyk has created this PR to upgrade hono from 4.8.8 to 4.9.8.

See this package in npm:
hono

See this project in Snyk:
https://app.snyk.io/org/kuohuanhuan/project/d967255a-3468-41b3-9209-3466fb3353ae?utm_source=github&utm_medium=referral&page=upgrade-pr
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@rnmeow @snyk-bot