Skip to content

Comments

Upgrade Next.js to next@canary#144

Open
timneutkens wants to merge 2 commits intoe18e:mainfrom
timneutkens:add/upgrade-next
Open

Upgrade Next.js to next@canary#144
timneutkens wants to merge 2 commits intoe18e:mainfrom
timneutkens:add/upgrade-next

Conversation

@timneutkens
Copy link
Contributor

Can you run CI with this version of Next.js? I did some local runs but curious to see what it looks like on CI.

Checklist

  • If updating UI/UX components ensure you have added screenshots or a gif or video of the changes to the PR description
  • If this is a dependabot PR that bumps a metaframework version, ensure that all package versions in the package match the versions installed by the metaframework version being bumped
  • If this is a dependabot PR that bumps a metaframework version in a starter-* package, ensure that the deps, and file content matches the output of the metaframeworks recommended starter/default project

@AlexanderKaran
Copy link
Collaborator

@timneutkens Sure let me just add a cancary option across the board to make this easier

@AlexanderKaran AlexanderKaran marked this pull request as ready for review February 23, 2026 13:10
@AlexanderKaran AlexanderKaran mentioned this pull request Feb 23, 2026
@AlexanderKaran
Copy link
Collaborator

Hi @timneutkens

Sorry for the wait. I got round to running our tempory canary checker here: #152

You can see the diff here

Screenshot 2026-02-23 at 9 25 35 pm
  • Increase in ops per second
  • Drop in latency ms
  • Increase in samples

All round a good fix in the SSR regard

cc @43081j

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.

2 participants