Skip to content

Commit 940a08b

Browse files
committed
Fixing Steps component to fix CI
1 parent ae4b07a commit 940a08b

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

src/content/docs/durable-objects/reference/durable-objects-migrations.mdx

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -57,7 +57,7 @@ To apply a Create migration:
5757

5858
2. Ensure you reference the correct name of the Durable Object class in your Worker code.
5959
3. Deploy the Worker.
60-
</Steps>
60+
</Steps>
6161

6262
<Details header="Create migration example">
6363

@@ -131,7 +131,7 @@ To apply a Delete migration:
131131
- The array `deleted_classes`, which contains the deleted Durable Object classes.
132132

133133
4. Deploy the Worker.
134-
</Steps>
134+
</Steps>
135135

136136
<Details header = "Delete migration example">
137137
To delete a Durable Object binding `DEPRECATED_OBJECT`, your `wrangler.toml / wrangler.json` file should look like the following:
@@ -238,7 +238,7 @@ To apply a Transfer migration:
238238

239239
2. Ensure you reference the name of the new, destination Durable Object class in your Worker code.
240240
3. Deploy the Worker.
241-
</Steps>
241+
</Steps>
242242

243243
<Details header = "Transfer migration example">
244244

@@ -294,4 +294,4 @@ You cannot enable a SQLite storage backend on an existing, deployed Durable Obje
294294
:::caution[Important]
295295
Durable Object migrations are atomic operations and cannot be gradually deployed. To provide early feedback to developers, new Worker versions with new migrations cannot be uploaded. Refer to [Gradual deployments for Durable Objects](/workers/configuration/versions-and-deployments/gradual-deployments/#gradual-deployments-for-durable-objects) for more information.
296296
:::
297-
```
297+

0 commit comments

Comments
 (0)