Skip to content

deps: raise hono to >=4.13.16 and @hono/node-server to >=2.1.6 (fixed releases of published advisories) #33241

Closed as duplicate

Description

@objectstack-fleet

repo:cloud#5 · hotlong · session_01Q4EjjPP1zuWBNq3nBXVei9

Filed on the maintainer's word, in seat session session_01Q4EjjPP1zuWBNq3nBXVei9: 「没必要走安全流程,直接升级卡」 and 「定位 p1」.

维护者速读

  1. 做什么:框架用的两个网络库 hono 和 @hono/node-server 有已公开的漏洞,修好的版本已经发布。把框架里这两个库的最低版本提上去,重新生成依赖锁文件,然后发版。
  2. 为什么:云端镜像运行时用的是框架打包的这两个库。云端自己已经升好了(cloud PR 读副本路由(read/write splitting):真要做的话,从查询路径开始,而不是从 datasource 上加个字段(#4468 移除 readReplicas 后的正式立项位) #4479),但要框架升级、发版,云端再跟着升级框架版本,才算真正修好。
  3. 风险:只是补丁版本的小升级,不改接口。
  4. 验收:锁文件里 hono 是 4.13.16 及以上、@hono/node-server 是 2.1.6 及以上;构建和测试全绿;osv 扫描不再报这两个库。
  5. 之后:发版后,云端升级框架版本(cloud 车道跟进)。
  6. 需要你做的:无。

Measured

Change

Raise both override floors to the first fixed release, keeping the upper bounds on the major boundary. Move the direct declarations in lockstep. Regenerate the lockfile so only these packages move. Run the build, the affected packages' tests, and the OSV check. Release through the normal changeset path.

Reader: triage sets the lane (priority:p1 is the maintainer's).

Activity

  1. objectstack-fleet commented on Nov 14, 2026

    @objectstack-fleet
    ContributorAuthor

    triage#1 · hotlong · session_01Q4EjjMnyLqJdzuktEmRPXH

    Path: none

    Triage: duplicate of #33211 · 2026-11-14T14:44Z

    This is the same work: hono → 4.13.16 and @hono/node-server → 2.1.6, after the scheduled OSV audit went red. #33211 (p1, domain:server, Area A5 in the pilot) carries it, and its PR #33225 has passed review and is landing. This card's extra ask, a framework release after the bump so cloud can move its pin (cloud PR #4479), is copied onto #33211.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    dependenciesPull requests that update a dependency filepriority:p1High: required for production / M2

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions