-
Couldn't load subscription status.
- Fork 92
ci: adjustments after next@16 stable release #3195
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
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -16,7 +16,3 @@ export async function proxy(request: NextRequest) { | |
| return response | ||
| } | ||
| } | ||
|
|
||
| export const config = { | ||
| runtime: 'nodejs', | ||
| } | ||
|
Comment on lines
-19
to
-22
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. this cause build failures now: Note that this test fixture was added yesterday specifically for next@16 while there were lot of Next.js PRs still in flight and I wasn't sure what the handling will be - see #3190 (review) |
||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -41,8 +41,10 @@ export function shouldHaveAppRouterNotFoundInPrerenderManifest() { | |
| export function shouldHaveAppRouterGlobalErrorInPrerenderManifest() { | ||
| // https://github.com/vercel/next.js/pull/82444 | ||
|
|
||
| // this is not used in any stable version yet | ||
| return isNextCanary() && nextVersionSatisfies('>=15.5.1-canary.4') | ||
| return ( | ||
| (isNextCanary() && nextVersionSatisfies('>=15.5.1-canary.4')) || | ||
| nextVersionSatisfies('>=16.0.0') | ||
| ) | ||
|
Comment on lines
+44
to
+47
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Another change that graduated from canary-only to be enabled in stable releases (this is used in our tests only to make correct assertions, it doesn't change actual support for it) |
||
| } | ||
|
|
||
| export function hasNodeMiddlewareSupport() { | ||
|
|
||
Uh oh!
There was an error while loading. Please reload this page.
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.
this is pretty much the change repeated in couple of places:
Resolve Next.js versionstep to be beforeDecide Node Version16.- use node@20, otherwise - use node@18 (and for next.js repo tests also use same logic to decide if default bundler is webpack or turbopack). We were checking if we testnext@canarybefore because minimum node version bump landed in v15 canaries (but only was released in v16 stable)everything else in github action workflows is just prettier auto-formatting which makes the diff messy