You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Update Next.js and the MCP server's hono for open advisories, and keep branch names out of the PR check scripts - #668
Updates the three dependencies on develop that still have open advisories, and closes a script injection in the PR check workflow.
Dependencies
next and eslint-config-next 16.4.1 → 16.4.6. 16.4.5 fixes two cache leaks across root params in 'use cache' functions (GHSA-mfr8-8qww-v76h, GHSA-vc7v-qv4w-wrv8, moderate); 16.4.6 is the current 16.4 patch. In yarn.lock only next and the @next/* packages change.
mcp-server: hono 4.13.11 → 4.13.18 and @hono/node-server 2.1.3 → 2.1.8. Both come in through @modelcontextprotocol/sdk 1.32.2, whose ranges (^4.11.4, ^1.19.9 || ^2.0.5) already allow them, so only those two entries change in bun.lock. This fixes:
@hono/node-server: GHSA-jpvv-r467-5p4w (a backslash in the path bypasses path-based checks) and GHSA-qv5m-9pm6-hqp3 (crash on ECONNRESET during a WebSocket upgrade), both moderate.
4.13.18 and 2.1.8 are the newest releases that are more than a week old; the fixes landed in 4.13.16 and 2.1.6.
After this, an OSV scan of yarn.lock and mcp-server/bun.lock finds no open advisories.
PR check workflow
pr-checks.yml expanded ${{ github.head_ref }} straight into its shell scripts. A branch name is chosen by whoever opens the PR, and Git allows names such as $(curl${IFS}…), so such a PR would run that command on the runner. The branch names now reach the scripts as environment variables, and the checks themselves are unchanged.
Checked locally, with the same steps as PR Checks
Node 24.22.1 and Yarn 1.22.22:
yarn install --frozen-lockfile
yarn lint: 0 errors. The 6 warnings are the same on develop.
yarn tsc --noEmit
tests/security: 311 passed.
tests/api: 547 passed.
tests/server-actions: 990 passed, 11 skipped.
Bun 1.4.4, in mcp-server:
bun install --frozen-lockfile; a plain bun install leaves the lockfile unchanged.
bun run typecheck
bun test: 90 passed.
bun run build
Summary by CodeRabbit
Chores
Updated project maintenance tooling and refined pull request checks. These changes do not alter the app’s user-facing functionality.
No actionable comments were generated in the recent review.
Walkthrough
The workflow passes source and target branch names to shell steps through environment variables. The branch check still rejects pull requests targeting main unless the source branch is develop. The next dependency and eslint-config-next devDependency versions both change from 16.4.1 to 16.4.6.
Suggested reviewers:fccview
Change: Other
Merge Risk: Minimal · up to cb7d2
This change updates Next.js dependencies and hardens PR check scripts against branch-name injection. No actionable merge-blocking risk was found.
Pre-merge checks: 4
Check name
Status
Explanation
Description Check
Check skipped - CodeRabbit’s high-level summary is enabled.
Title check
The title names the two main changes: updating Next.js and the MCP server's hono dependencies for open advisories, and keeping branch names out of the PR check scripts. The raw summary shows the workf…
Linked Issues check
Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check
Check skipped because no linked issues were found for this pull request.
Full details: Title check
Explanation
The title names the two main changes: updating Next.js and the MCP server's hono dependencies for open advisories, and keeping branch names out of the PR check scripts. The raw summary shows the workflow change (branch names passed via HEAD_REF and BASE_REF environment variables) and the package.json bumps for next and eslint-config-next. The title is specific and matches the changeset. It is long at 111 characters and 20 words, but it still conveys the primary changes. The raw summary does not list the mcp-server hono update, but the excluded lock files and PR objectives cover it.
Finishing Touches
Generate unit tests (beta)
Create a new PR
Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.
File: No configuration file from this repository applied
Commit: Unavailable
Layers: Organization UI
Review profile: CHILL
Plan: Advanced
Run ID: d50f2229-21fe-4e55-aedf-8d70cbb436c7
Commits
Reviewing files that changed from the base of the PR and between cdc4cf9 and cb7d2d2.
Files ignored due to path filters: 2
mcp-server/bun.lock is excluded by !**/*.lock
yarn.lock is excluded by !**/yarn.lock, !**/*.lock
Files selected for processing: 2
.github/workflows/pr-checks.yml
package.json
Included review availability: This review used your included allowance. Your plan provides up to 8 included reviews per hour; 7 remain after this review.
Thank you!
The nextjs cve was published right after I released 😮💨♥️
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Updates the three dependencies on
developthat still have open advisories, and closes a script injection in the PR check workflow.Dependencies
nextandeslint-config-next16.4.1 → 16.4.6. 16.4.5 fixes two cache leaks across root params in'use cache'functions (GHSA-mfr8-8qww-v76h, GHSA-vc7v-qv4w-wrv8, moderate); 16.4.6 is the current 16.4 patch. Inyarn.lockonlynextand the@next/*packages change.mcp-server:
hono4.13.11 → 4.13.18 and@hono/node-server2.1.3 → 2.1.8. Both come in through@modelcontextprotocol/sdk1.32.2, whose ranges (^4.11.4,^1.19.9 || ^2.0.5) already allow them, so only those two entries change inbun.lock. This fixes:csrf()andtext/ping), GHSA-4h7h-rv7c-7m2v (validator('form')and multipart), GHSA-4m76-xfj5-7975 (mount()middleware bypass) and GHSA-h7mg-cq63-vhpq (RegExpRouter wildcard middleware), all moderate, plus GHSA-3gg2-335m-rxc6 (low).ECONNRESETduring a WebSocket upgrade), both moderate.4.13.18 and 2.1.8 are the newest releases that are more than a week old; the fixes landed in 4.13.16 and 2.1.6.
After this, an OSV scan of
yarn.lockandmcp-server/bun.lockfinds no open advisories.PR check workflow
pr-checks.ymlexpanded${{ github.head_ref }}straight into its shell scripts. A branch name is chosen by whoever opens the PR, and Git allows names such as$(curl${IFS}…), so such a PR would run that command on the runner. The branch names now reach the scripts as environment variables, and the checks themselves are unchanged.Checked locally, with the same steps as PR Checks
yarn install --frozen-lockfileyarn lint: 0 errors. The 6 warnings are the same ondevelop.yarn tsc --noEmittests/security: 311 passed.tests/api: 547 passed.tests/server-actions: 990 passed, 11 skipped.mcp-server:bun install --frozen-lockfile; a plainbun installleaves the lockfile unchanged.bun run typecheckbun test: 90 passed.bun run buildSummary by CodeRabbit