Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion pages/cloudflare/_meta.json
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,8 @@
"examples": "",
"community": "Community projects",
"troubleshooting": "",
"migrate-from-0.3-to-0.4": "Migrate from 0.3",
"migrate-from-0.4-to-0.5": "Migrate from 0.4",
"migrate-from-0.3-to-0.4": "",
"0.3": "Release 0.3",
"migrate-from-0.2-to-0.3": "",
"0.2": "Release 0.2"
Expand Down
4 changes: 2 additions & 2 deletions pages/cloudflare/migrate-from-0.3-to-0.4.mdx
Original file line number Diff line number Diff line change
@@ -1,9 +1,9 @@
import { SITE } from '../../config';
import { Callout } from 'nextra/components';

### Migrate from 0.3 (to 0.4)
### Migrate from 0.3 to 0.4

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

##### `initOpenNextCloudflareForDev`
Expand Down
3 changes: 3 additions & 0 deletions pages/cloudflare/migrate-from-0.4-to-0.5.mdx
Original file line number Diff line number Diff line change
@@ -0,0 +1,3 @@
### Migrate from 0.4 (to 0.5)

`@opennextjs/cloudflare@0.5.0` did not introduce any breaking change, meaning that there are no migration steps from `0.4` to `0.5`.