-
Notifications
You must be signed in to change notification settings - Fork 35
chore: upgrade next to 14 #4875
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
base: main
Are you sure you want to change the base?
Conversation
@YazeedLoonat I took a stab at looking at your next upgrade and kept running into issues. I had better success with upgrading to NextJS 14. I can build the public site successfully locally but it is failing in Netlify because we need to upgrade the node version there. However, partner still doesn't work. We can't upgrade to 15 until we upgrade React to 19 which would be a big lift. Don't know if it makes sense to just go to 14 and skip the 13 minor version |
✅ Deploy Preview for bloom-exygy-dev ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for bloom-demo-public ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
This reverts commit 18e9428.
✅ Deploy Preview for bloom-demo-partners ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Public and partners are building in Netlify!!! |
This PR addresses #(insert-number-here)
Description
Please include a summary of the change and which issue(s) is addressed.
How Can This Be Tested/Reviewed?
Provide instructions so we can review, including any needed configuration, and the test cases that need to be QAd.
Author Checklist:
yarn generate:client
and/or created a migration when requiredReview Process: