Skip to content

Comments

Upgrade Next.js to next@canary#144

Draft
timneutkens wants to merge 1 commit intoe18e:mainfrom
timneutkens:add/upgrade-next
Draft

Upgrade Next.js to next@canary#144
timneutkens wants to merge 1 commit 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

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