Skip to content

Commit 241f332

Browse files
update Cloudflare docs to include 0.5 (#80)
1 parent 814f261 commit 241f332

File tree

3 files changed

+7
-3
lines changed

3 files changed

+7
-3
lines changed

pages/cloudflare/_meta.json

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,8 @@
77
"examples": "",
88
"community": "Community projects",
99
"troubleshooting": "",
10-
"migrate-from-0.3-to-0.4": "Migrate from 0.3",
10+
"migrate-from-0.4-to-0.5": "Migrate from 0.4",
11+
"migrate-from-0.3-to-0.4": "",
1112
"0.3": "Release 0.3",
1213
"migrate-from-0.2-to-0.3": "",
1314
"0.2": "Release 0.2"

pages/cloudflare/migrate-from-0.3-to-0.4.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,9 @@
11
import { SITE } from '../../config';
22
import { Callout } from 'nextra/components';
33

4-
### Migrate from 0.3 (to 0.4)
4+
### Migrate from 0.3 to 0.4
55

6-
The `@opennextjs/cloudflare@0.4.0` introduced a new `initOpenNextCloudflareForDev` utility and made `getCloudflareContext` synchronous,
6+
`@opennextjs/cloudflare@0.4.0` introduced a new `initOpenNextCloudflareForDev` utility and made `getCloudflareContext` synchronous,
77
we'll explore those two differences below, and how they effect applications built using `0.3.x` versions of the adapter.
88

99
##### `initOpenNextCloudflareForDev`
Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,3 @@
1+
### Migrate from 0.4 (to 0.5)
2+
3+
`@opennextjs/cloudflare@0.5.0` did not introduce any breaking change, meaning that there are no migration steps from `0.4` to `0.5`.

0 commit comments

Comments
 (0)