-
-
Notifications
You must be signed in to change notification settings - Fork 6.5k
chore(next): bump version of nextjs and related deps #8441
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
👋 Codeowner Review RequestThe following codeowners have been identified for the changed files: Team reviewers: @nodejs/nodejs-website @nodejs/web-infra Please review the changes when you have a chance. Thank you! 🙏 |
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull request overview
This PR updates Next.js from version 16.0.10 to 16.1.1 and React from 19.2.1 to 19.2.3, along with related dependency updates to maintain compatibility and bring in new features.
Key Changes
- React updated from 19.2.1 to 19.2.3 (patch version bump)
- Next.js updated from 16.0.10 to 16.1.1 (minor version bump)
- OpenTelemetry packages updated to newer versions for improved observability
- Vercel analytics and tooling packages updated
- Build tools (turbo, wrangler) updated to latest versions
Reviewed changes
Copilot reviewed 3 out of 4 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| pnpm-workspace.yaml | Updates React version in catalog from ^19.2.1 to ^19.2.3 |
| package.json | Updates turbo from 2.6.1 to 2.7.1 |
| apps/site/package.json | Updates Next.js to 16.1.1, OpenTelemetry packages to ~0.208.0/~2.2.0, Vercel packages, next-intl to ~4.6.1, wrangler to ^4.56.0, and Next.js ESLint packages to 16.1.1 |
| pnpm-lock.yaml | Reflects all dependency version changes with consistent peer dependency resolution |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
Is there a reason we're doing this by hand rather than allowing Dependabot to its job for us? |
Yes, I want to dig more into bundle size improvements using features introduced in 16.1 (i.e. |
📦 Build Size ComparisonSummary
Changes➕ Added Assets (24)
➖ Removed Assets (25)
|
|
I see -- should this be a draft then if you're just using it to explore the new features? And then once Dependabot does the actual updates, we can use those features? |
I'd prefer to land this, since it'll allow me to |
|
I'm not sure I follow why this needs to land to allow you to do that? Why can't you bump the packages locally on main, and then compare that against other changes you wish to make locally? But yes, if we do need to do dependency updates sooner, I'd prefer that Dependabot is still used for it, so that the team can review those bumps in isolation, rather than a bunch of bumps in a single PR that is much harder to review safely. |
Noted, no need to run early, I think it'll run soon anyway.
I suppose that's better. We can wait the few days for Dependabot to run. |
This PR bumps the dependencies related to Next.js, bringing in new features + smaller install bundles.
Notably,
next experimental-analyzewill allow us to better identify bundle improvements.