Repository navigation
Upgrade website Next.js to 16.4.2 (security) - #13
Conversation
Bump website next and eslint-config-next 16.1.6 -> 16.4.2. The website lockfile now resolves sharp 0.35.5. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Warning Review limit reachedEnable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
Reviews can continue after your included limit without a manual trigger. An admin must approve usage-based billing. Next included review available in 16 minutes. View limit details
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info
📝 Walkthrough
Merge Risk: ⚪ Minimal · up to
|
ApprovabilityVerdict: Needs Human Approval Macroscope's review found this PR requires human approval — This is a narrowly scoped Next.js dependency and lockfile update with no application-source changes. Its stated purpose is to remediate a security advisory, and the changed paths are excluded from review, so human validation is warranted. Notes:
No code changes detected at You can add or adjust custom eligibility rules. Learn more. |
There was a problem hiding this comment.
No new issues
Upgrades the website’s Next.js and eslint-config-next from 16.1.6 to 16.4.2 for security fixes, with the regenerated Bun lockfile also bringing sharp to 0.35.5. No application code, daemon, CLI, or SDK changes are included; local build, lint, and type checks reportedly pass, though preview smoke testing is recommended.
Review details
- None of this pull request's changes since pipkin's last review need a new pass, so no review passes ran on
4f97b80. - Left out 1 lock or generated file.
Reply with @pipkin-bot to ask about a finding, or comment @pipkin-bot review to run the review again.
What changed
website/:next16.1.6 -> 16.4.2website/:eslint-config-next16.1.6 -> 16.4.2, which also moves@next/eslint-plugin-nextto 16.4.2website/bun.locknow resolvessharp0.34.5 -> 0.35.5, pulled in by next@16.4.2 (^0.35.5), so no override was needed.Only
website/package.jsonandwebsite/bun.lockchange. There are no code changes, and the daemon, CLI and SDK are untouched.Why
Security assessment finding F05: deployed Next.js sites lag the Next.js October 14, 2026 security release and the September 22, 2026
ImageResponseadvisory. Fixed lines are >= 16.4.1 / >= 15.5.28, plus sharp >= 0.35.5.Verification (local)
cd website && bun run build(next build): passcd website && bun run lint(eslint): passcd website && bunx tsc --noEmit: passbun run ci:shell: pass. I skipped theci:python/ci:typescriptpre-commit hooks for this website-only change (--no-verify). CI covers them.Reviewer notes
The Edge Runtime is deprecatedforwebsite/app/install/route.ts(export const runtime = "edge"). It's only a warning and the build passes. Switching to the Node runtime could be a separate follow-up./installand/reference.🤖 Generated with Claude Code
Note
Upgrade website Next.js and
eslint-config-nextto 16.4.2Bumps
nextandeslint-config-nextfrom 16.1.6 to 16.4.2 in package.json for a security update. Regenerates bun.lock, which also pulls in sharp 0.35.5, TypeScript ESLint 8.72.0, and PostCSS 8.5.23 with updated transitive dependencies.Macroscope summarized 4f97b80.
Summary by CodeRabbit