Repository navigation
fix(deps): patch @hono/node-server to 2.1.6 - #1656
cipherstash-agent wants to merge 1 commit into
Conversation
Two advisories (CVE-2026-126210, CVE-2026-126343) affect @hono/node-server >= 2.0.0, < 2.1.6, which @modelcontextprotocol/sdk pulls into @cipherstash/wizard. The SDK's range already admits 2.1.6, 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
There was a problem hiding this comment.
Review attestation
Reviewed 935f77f · posted from Claude Code · claude-opus-5-5 · effort medium
Sources: code-review · claude-opus-5-5; review-cross-check verify agents · claude-opus-5-5
Skills: code-review, rust-security (not applicable: no Rust in the diff), review-cross-check, review-post
Checked: every @hono/node-server resolution is 2.1.6; integrities for @hono/node-server@2.1.6 and rollup@4.68.0 match the registry; pnpm install --lockfile-only (pnpm 10.33.2) on head produces no diff; all moved versions clear the 7-day cooldown.
Findings (4): 4 minor — 3 inline, 1 below.
languages/typescript/packages/nextjs/package.json:56(outside diff) minor The rollup bump leaves the published@cipherstash/nextjsoptionalDependency pin"@rollup/rollup-linux-x64-gnu": "4.67.4"behind; Dependabot has moved it in lockstep with rollup every time (5c17dba, 589abf6). The lockfile now carries both 4.67.4 (nextjs pin only,pnpm-lock.yaml:400-402,:2171) and 4.68.0 natives. Keep rollup at 4.67.4, or bump the pin with a@cipherstash/nextjschangeset.
Source: code-review · claude-opus-5-5, verified by review-cross-check
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 This security patch also moves rollup 4.67.4 → 4.68.0 (and all 25 @rollup/rollup-* natives) for every vite/vitest consumer; 4.68.0 was 7d 2h old at commit time against minimumReleaseAge: 10080. The ride-along is not forced: editing only the three @hono/node-server sites on base passes pnpm install --frozen-lockfile --lockfile-only and a non-frozen re-resolve leaves it byte-identical, contrary to the PR body. Regenerate the lockfile with only the target moved and leave rollup to Dependabot.
Source: code-review · claude-opus-5-5, verified by review-cross-check
Generated by Claude Code
| debug: 4.4.3 | ||
| env-paths: 3.0.0 | ||
| semver: 7.8.5 | ||
| semver: 7.8.6 |
There was a problem hiding this comment.
minor gel@2.2.0's resolved semver moves 7.8.5 → 7.8.6 here, leaving two semver copies; the PR body only says semver@7.8.6 was "added as an optional snapshot". Low impact (gel is an optional peer of drizzle-orm), but it is an undisclosed change to an existing package's dependency; the narrow lockfile from the rollup comment drops it too.
Source: code-review · claude-opus-5-5, verified by review-cross-check
Generated by Claude Code
| optional: true | ||
|
|
||
| '@hono/node-server@2.1.5(hono@4.13.14)': | ||
| '@hono/node-server@2.1.6(hono@4.13.14)': |
There was a problem hiding this comment.
minor This snapshot key and the @modelcontextprotocol/sdk reference (line 4917) embed the hono@4.13.14 peer, and #1657 rewrites the same two lines to 2.1.5(hono@4.13.16): git merge-tree of the two heads conflicts on exactly these hunks. Resolving by taking this side yields 2.1.6(hono@4.13.14) with only hono@4.13.16 installed, and --frozen-lockfile still passes, so CI will not catch it. Fold both bumps into one PR, or rebase the second and regenerate with pnpm install --lockfile-only rather than hand-resolving.
Source: code-review · claude-opus-5-5, verified by review-cross-check
Generated by Claude Code
Summary
Patches
@hono/node-serverfrom 2.1.5 to 2.1.6 inpnpm-lock.yaml. Version 2.1.5 is affected by two advisories. This is a lockfile-only change:@modelcontextprotocol/sdk@1.32.2(pulled in by@cipherstash/wizard, directly and through@anthropic-ai/claude-agent-sdk) already allows^2.0.5, so no manifest or override changes.Advisories
>= 2.0.0, < 2.1.6>= 2.0.0, < 2.1.6Changes
pnpm-lock.yamlOther packages that moved:
pnpm update -r @hono/node-serveralso 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-gnudependency, so that entry is gone too. The target did not require these moves. Trying to pin rollup back withpnpm update -r rollup@4.67.4left the lockfile unchanged, so they are kept here and called out for review. A scoped override would avoid them, but it is a heavier change that has to be removed later.Verification
935f77f): every location that resolves@hono/node-serverresolves 2.1.6, with no vulnerable version left.pnpm install --frozen-lockfile --lockfile-only --ignore-scriptspasses (pnpm 10.33.2, as pinned inpackageManager).Related
honoitself (4.13.14, advisories fixed in 4.13.16) is handled in a separate PR.Generated by Claude Code