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
Bumps next to 15.5.18 to pick up the fix for GHSA-26hh-7cqf-hhc6, a high-severity (CVSS 7.5) Middleware/Proxy bypass in App Router applications via segment-prefetch routes (incomplete-fix follow-up). Mirrors #8281: updates the @clerk/nextjs devDep, the Next.js integration templates, the @clerk/msw peer floor, and the pnpm-workspace.yaml minimum-release-age exclusion. Peer range left as-is; users on the App Router should upgrade to 15.5.18 or later.
Bump `next` to `15.5.18` to pick up the fix for GHSA-26hh-7cqf-hhc6,
a high-severity (CVSS 7.5) Middleware/Proxy bypass in App Router
applications via segment-prefetch routes.
Reviewing files that changed from the base of the PR and between f684acb and ac5aac4.
📒 Files selected for processing (2)
packages/msw/package.json
packages/nextjs/package.json
✅ Files skipped from review due to trivial changes (1)
packages/nextjs/package.json
🚧 Files skipped from review as they are similar to previous changes (1)
packages/msw/package.json
📝 Walkthrough
Walkthrough
This pull request adds a changeset for a Next.js security fix (GHSA-26hh-7cqf-hhc6), bumps Next.js in multiple integration templates (including a 16.2.6 bump for cache-components), tightens package constraints (packages/msw peerDependency and packages/nextjs devDependency), and updates pnpm-workspace.yaml's excluded Next.js entry to 15.5.18.
The title accurately summarizes the main change: updating Next.js to patched versions (15.5.18 and 16.2.6) to address the GHSA-26hh-7cqf-hhc6 security vulnerability.
Description check
✅ Passed
The description is directly related to the changeset, detailing the security fix and all updated components including devDependencies, templates, peer floors, and workspace configuration.
Docstring Coverage
✅ Passed
No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check
✅ Passed
Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check
✅ Passed
Check skipped because no linked issues were found for this pull request.
✏️ Tip: You can configure your own custom pre-merge checks in the settings.
Comment @coderabbitai help to get the list of available commands and usage tips.
The next-cache-components template floor at ^16.2.3 still permitted
versions affected by GHSA-26hh-7cqf-hhc6 (16.0.0–16.2.5). Raise it
to ^16.2.6 and tighten the changeset wording to call out the 16.x
patched line.
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.
Bumps
nextto15.5.18to pick up the fix for GHSA-26hh-7cqf-hhc6, a high-severity (CVSS 7.5) Middleware/Proxy bypass in App Router applications via segment-prefetch routes (incomplete-fix follow-up). Mirrors #8281: updates the@clerk/nextjsdevDep, the Next.js integration templates, the@clerk/mswpeer floor, and thepnpm-workspace.yamlminimum-release-age exclusion. Peer range left as-is; users on the App Router should upgrade to15.5.18or later.