Unverified Commit dcf11d11 authored by Joseph's avatar Joseph Committed by GitHub

docs: clarify that next upgrade is for 16.1.x+ (#90435)

Closes: https://github.com/vercel/next.js/issues/90425
parent c61d96e0
...@@ -30,7 +30,7 @@ yarn next upgrade ...@@ -30,7 +30,7 @@ yarn next upgrade
bunx next upgrade bunx next upgrade
``` ```
Next.js 15 and earlier do not support the `upgrade` command and need to use a separate package instead: Versions before Next.js 16.1.0 do not support the `upgrade` command and need to use a separate package instead:
```bash filename="Terminal" ```bash filename="Terminal"
npx @next/codemod@canary upgrade latest npx @next/codemod@canary upgrade latest
......
...@@ -409,6 +409,7 @@ The generated `.cpuprofile` files can be opened in Chrome DevTools (Performance ...@@ -409,6 +409,7 @@ The generated `.cpuprofile` files can be opened in Chrome DevTools (Performance
| Version | Changes | | Version | Changes |
| --------- | ------------------------------------------------------------------------------- | | --------- | ------------------------------------------------------------------------------- |
| `v16.1.0` | Add the `next upgrade` command |
| `v16.1.0` | Add the `next experimental-analyze` command | | `v16.1.0` | Add the `next experimental-analyze` command |
| `v16.0.0` | The JS bundle size metrics have been removed from `next build` | | `v16.0.0` | The JS bundle size metrics have been removed from `next build` |
| `v15.5.0` | Add the `next typegen` command | | `v15.5.0` | Add the `next typegen` command |
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment