Repository navigation
fix(deps): align eslint-config-next and require patched Node.js - #37
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
next was already bumped to 15.5.28 in #36; this aligns eslint-config-next to the same version. Also adds an engines field requiring Node.js >= 22.23.4, the first 22.x release with the October 21, 2026 Node.js security fixes (CVE-2026-111497 Brotli RCE, TLS/DNS hostname bypasses). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0198wDAWdEeCmkHRVy48quSm
Jeffreyhung
force-pushed
the
security/bump-next-15.5.28
branch
from
October 22, 2026 21:10
c93db0b to
48b5e7e
Compare
This branch was successfully deployed
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Why
Node.js: the October 21, 2026 Node.js security release fixes 10 CVEs, including a Brotli decoder RCE (CVE-2026-111497) and TLS/DNS hostname verification bypasses. The repo didn't pin a Node version, so this adds
engines.node: ">=22.23.4"(first patched 22.x) to make the requirement explicit.Next.js:
nextwas already bumped to15.5.28in #36 (fixes CVE-2026-96889 and GHSA-p3m5-59mp-jv5r). This alignseslint-config-next, which was left on15.5.18.Changes
engines.node: ">=22.23.4"eslint-config-next:15.5.18→15.5.28pnpm-lock.yamlTesting
pnpm install --frozen-lockfileandpnpm buildpass locally.Follow-up
Confirm the deployment's Node.js runtime is on a patched release (22.23.4, 24.22.1, or 26.12.1) and redeploy.
https://claude.ai/code/session_0198wDAWdEeCmkHRVy48quSm
Generated by Claude Code