Repository navigation
fix(deps): patch hono to 4.13.16 - #1657
cipherstash-agent wants to merge 1 commit into
Conversation
Five advisories (CVE-2026-126355, -126356, -126357, -126358, -126359) affect hono up to 4.13.15, which @modelcontextprotocol/sdk and @hono/node-server pull into @cipherstash/wizard. Their ranges already admit 4.13.16, so this is a lockfile-only update. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_012Jmn7p74Yr1hRMy5SpiRj5
|
|
Important Review skippedReview was skipped due to path filters ⛔ Files ignored due to path filters: 1
CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including
 |
cipherstash-agent
left a comment
cipherstash-agent
left a comment
There was a problem hiding this comment.
Review attestation
Reviewed 15f1063 · posted from Claude Code (scheduled routine) · claude-opus-5-5 · effort medium
Sources: code-review · claude-opus-5-5
Skills: code-review, rust-security (no Rust in diff — not applicable), review-cross-check, review-post
Findings (2): 2 minor — 2 inline.
Checked, no finding: the lockfile integrity hashes for hono 4.13.16, rollup 4.68.0, @rollup/rollup-linux-x64-gnu 4.68.0 and semver 7.8.6 match the npm registry, and every new version clears the 7-day minimumReleaseAge. Every hono resolution is 4.13.16. No changeset is needed for the lockfile-only change as it stands.
Generated by Claude Code
| @@ -5260,46 +5261,49 @@ snapshots: | |||
| '@rollup/rollup-linux-x64-gnu@4.67.4': | |||
There was a problem hiding this comment.
minor pnpm update -r hono moved vite's rollup to 4.68.0, but @cipherstash/nextjs still pins "@rollup/rollup-linux-x64-gnu": "4.67.4" (languages/typescript/packages/nextjs/package.json:56, importer at pnpm-lock.yaml:401), so this 4.67.4 entry is now kept alive only by that pin. linux-x64 installs fetch a 4.67.4 binary that nothing loads, alongside rollup's own 4.68.0 one, and no check catches the mismatch. Keep rollup at 4.67.4 here, or bump the pin to 4.68.0, which edits a published manifest and needs a @cipherstash/nextjs patch changeset.
Source: code-review · claude-opus-5-5
Generated by Claude Code
|
|
||
| rollup@4.67.4: | ||
| resolution: {integrity: sha512-Lsv3oKcz5jgOQJej/p7nfwbVEdAbDT+z6OPf/SCdI+nF+q2ENp0pTKT35ZwXAmH8g45mfrIiJeEyAqKYSYoL9Q==} | ||
| rollup@4.68.0: |
There was a problem hiding this comment.
minor The hono patch also carries changes the advisories do not need: rollup 4.67.4 → 4.68.0 on every platform, a new semver@7.8.6 for gel, and the dropped @napi-rs/lzma-linux-x64-gnu. The rollup move causes the pin drift flagged on line 5261 and overlaps with #1656. Limit the lockfile change to hono and the @hono/node-server peer snapshots.
Source: code-review · claude-opus-5-5
Generated by Claude Code
Summary
Patches
honofrom 4.13.14 to 4.13.16 inpnpm-lock.yaml. Version 4.13.14 is affected by five advisories. This is a lockfile-only change.honocomes in through@modelcontextprotocol/sdk@1.32.2(^4.11.4) and@hono/node-server(peer^4), and both ranges already allow 4.13.16. Those packages are pulled in by@cipherstash/wizard.Advisories
>= 4.5.1, <= 4.13.15>= 4.1.4, <= 4.13.15< 4.13.16< 4.13.16>= 3.12.0, <= 4.13.15Changes
pnpm-lock.yamlOther packages that moved:
pnpm update -r honoalso re-resolvedrollup4.67.4 → 4.68.0 (a transitive build-time dependency) and addedsemver@7.8.6as an optional snapshot. Rollup 4.68.0 drops its optional@napi-rs/lzma-linux-x64-gnuentry. The target did not require these moves;pnpm updatemakes them for any package in this lockfile. The same moves appear in #1656, so whichever PR merges second needs only a trivial lockfile rebase.Verification
15f1063): every location that resolveshonoresolves 4.13.16, with no vulnerable version left.pnpm install --frozen-lockfile --lockfile-only --ignore-scriptspasses (pnpm 10.33.2, as pinned inpackageManager).Related
@hono/node-server2.1.5 → 2.1.6, which also touchespnpm-lock.yaml.Generated by Claude Code