Skip to content

Upgrade starter to Next.js 16.4 canary - #22

Merged
aurorascharff merged 1 commit into
startfrom
codex/upgrade-next-16-4-canary-start
Oct 27, 2026
Merged

aurorascharff merged 1 commit into
startfrom
codex/upgrade-next-16-4-canary-start

Conversation

@aurorascharff

Copy link
Copy Markdown
Collaborator

Summary

  • upgrade Next.js, eslint-config-next, and @next/playwright to 16.4.0-canary.63
  • upgrade @playwright/test to 1.64.1
  • migrate the stabilized navigation API import
  • retain the updated Next.js agent guidance generated by the canary

Verification

  • next typegen
  • tsc --noEmit
  • lint (passes with four pre-existing warnings)
  • next dev plus /_next/mcp diagnostics and browser smoke test
  • Playwright: 12 passed, 9 failed; focused testing on untouched start reproduced the instant-navigation assertion failures, and the starter home route still contains the intentional placeholder used by the track scenarios

Canary note

next build stalls during Turbopack compilation on 16.4.0-canary.63. The untouched 16.4.0-canary.45 baseline compiles, so this appears to be a canary regression rather than a project migration issue.

@vercel

vercel Bot commented Oct 27, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
next-beats Ready Ready Preview, v0 Oct 27, 2026 6:05pm UTC

@socket-security

Copy link
Copy Markdown

@aurorascharff
aurorascharff merged commit 1188db7 into start Oct 27, 2026
5 of 6 checks passed
@aurorascharff
aurorascharff deleted the codex/upgrade-next-16-4-canary-start branch October 27, 2026 18:13

This branch was successfully deployed

1 active deployment
Preview — 54b3ee8f Deployed Oct 27, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant