Document that alarms have been re-enabled for SQLite backed DOs

src/content/changelogs/durable-objects.yaml

@@ -5,6 +5,10 @@ productLink: "/durable-objects/"
 productArea: Developer platform
 productAreaLink: /workers/platform/changelog/platform/
 entries:
+  - publish_date: "2024-10-07"
+    title: Alarms re-enabled in (beta) SQLite-backed Durable Object classes
+    description: |-
+      The issue identified with [alarms](/durable-objects/api/alarms/) in [beta Durable Object classes with a SQLite storage backend](/durable-objects/best-practices/access-durable-objects-storage/#sqlite-storage-backend) has been resolved and alarms have been re-enabled.
   - publish_date: "2024-09-27"
     title: Alarms disabled in (beta) SQLite-backed Durable Object classes
     description: |-

src/content/docs/durable-objects/api/alarms.mdx

@@ -8,12 +8,6 @@ sidebar:
 
 import { Type } from "~/components";
 
-:::note[Alarms disabled for SQLite in Durable Objects Beta]
-
-An issue was identified with [alarms](/durable-objects/api/alarms/) in [beta Durable Object classes with a SQLite storage backend](/durable-objects/best-practices/access-durable-objects-storage/#sqlite-storage-backend). Alarms have been temporarily disabled for only SQLite-backed Durable Objects while a fix is implemented. Alarms in Durable Objects with default, key-value storage backend are unaffected and continue to operate.
-
-:::
-
 ## Background
 
 Durable Objects alarms allow you to schedule the Durable Object to be woken up at a time in the future. When the alarm's scheduled time comes, the `alarm()` handler method will be called. Alarms are modified using the [Storage API](/durable-objects/api/storage-api/), and alarm operations follow the same rules as other storage operations.

src/content/docs/durable-objects/api/storage-api.mdx

@@ -201,12 +201,6 @@ The `put()` method returns a `Promise`, but most applications can discard this p
 
   * This is similar to normal behavior from automatic write coalescing. If there are any pending writes in the write buffer (including those submitted with [the `allowUnconfirmed` option](/durable-objects/api/storage-api/#supported-options-1)), the returned promise will resolve when they complete. If there are no pending writes, the returned promise will be already resolved.
 
-:::note[Alarms disabled for SQLite in Durable Objects Beta]
-
-An issue was identified with [alarms](/durable-objects/api/alarms/) in [beta Durable Object classes with a SQLite storage backend](/durable-objects/best-practices/access-durable-objects-storage/#sqlite-storage-backend). Alarms have been temporarily disabled for only SQLite-backed Durable Objects while a fix is implemented. Alarms in Durable Objects with default, key-value storage backend are unaffected and continue to operate.
-
-:::
-
 ### getAlarm
 
 * <code>getAlarm(options <Type text='Object' /> <MetaInfo text='optional' />)</code>: <Type text='Promise<Number | null>' />

src/content/docs/durable-objects/index.mdx

@@ -35,12 +35,6 @@ Storage API billing is not enabled for Durable Object classes using SQLite stora
 
 :::
 
-:::note[Alarms disabled for SQLite in Durable Objects Beta]
-
-An issue was identified with [alarms](/durable-objects/api/alarms/) in [beta Durable Object classes with a SQLite storage backend](/durable-objects/best-practices/access-durable-objects-storage/#sqlite-storage-backend). Alarms have been temporarily disabled for only SQLite-backed Durable Objects while a fix is implemented. Alarms in Durable Objects with default, key-value storage backend are unaffected and continue to operate.
-
-:::
-
 ***
 
 ## Features