Skip to content

Commit f2949a8

Browse files
authored
[docs] Fix migration guide upgrade command (#5021)
* Fix upgrade command * Fix upgrade command * Fix upgrade command
1 parent 7e7e346 commit f2949a8

File tree

3 files changed

+3
-3
lines changed

3 files changed

+3
-3
lines changed

packages/docs/content/v4/changelog.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ This migration guide aims to list the breaking changes in Zod 4 in order of high
1111
{/* To give the ecosystem time to migrate, Zod 4 will initially be published alongside Zod v3.25. To use Zod 4, upgrade to `zod@3.25.0` or later: */}
1212

1313
```
14-
npm upgrade zod@^4.0.0
14+
npm install zod@^4.0.0
1515
```
1616

1717
{/* Zod 4 is available at the `"/v4"` subpath:

packages/docs/content/v4/index.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,7 @@ Huge thanks to [Clerk](https://go.clerk.com/zod-clerk), who supported my work on
2424
To upgrade:
2525

2626
```
27-
npm upgrade zod@^4.0.0
27+
npm install zod@^4.0.0
2828
```
2929

3030

packages/docs/content/v4/versioning.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ import { Callout } from "fumadocs-ui/components/callout";
1414
To upgrade to Zod 4:
1515

1616
```
17-
npm upgrade zod@^4.0.0
17+
npm install zod@^4.0.0
1818
```
1919

2020
If you are using Zod 4, your existing imports (`"zod/v4"` and `"zod/v4-mini"`) will continue to work forever. However, after upgrading, you can *optionally* rewrite your imports as follows:

0 commit comments

Comments
 (0)