-
-
Notifications
You must be signed in to change notification settings - Fork 110
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
Update Next.js framework to v10.0.5 (from v10.0.0) #243
Conversation
…loy correctly (this wasn't an issue just before... did upgrading Next or change the tsconfig file changed the behaviour?)
✅ Deployment SUCCESS |
✅ Deployment SUCCESS |
❌ Deployment FAILED |
✅ Deployment SUCCESS |
❌ Deployment FAILED |
❌ E2E tests FAILED for commit 33a913a previously deployed at https://nrn-v2-mst-aptd-at-lcz-sty-c1-93v2jfnst.vercel.app |
d1bbe70
to
b7b7b7a
Compare
Previous attempts to migrate to v10.0.5 failed. See vercel/next.js#20950
Attempting again, with a
minimal reproduction(due to reverting commits in base branch, tons of changes are now included in this PR).Summary:
Status
We can safely upgrade to v10.0.3, but not higher than that.
This PR was meant to be a test, and will be closed.