chore: upgrade nextjs & react for all webapps #2081
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
@cprussin is attempting to deploy a commit to the Pyth Network Team on Vercel. A member of the Team first needs to authorize it. |
cprussin
force-pushed
the
upgrade-next-and-react
branch
from
56f2858 to
dc61d3b
Compare
cprussin
force-pushed
the
upgrade-next-and-react
branch
from
dc61d3b to
e6f1593
Compare
cprussin
force-pushed
the
upgrade-next-and-react
branch
from
e6f1593 to
acc12a1
Compare
cprussin
force-pushed
the
upgrade-next-and-react
branch
from
acc12a1 to
d1a13fe
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR upgrades all nextjs apps to next.js v15 which was released last week.
Next is currently recommending all apps on v15 to migrate to React 19, which has not officially been released and is still in RC phase, see the nextjs blog for details. In following the advice, this PR also upgrades the react version.
This PR also introduces usage of the pnpm catalog feature to manage versions that should be shared across packages in the monorepo.