Changelog for pause & purge (#21134)

* Updated changelog for pause and purge

* Updated changelog entry

* Fixed capitalization

* typos

* Made less verbose

* Added link

* Added links

* Update src/content/changelog/queues/2025-03-25-pause-purge-queues.mdx

Co-authored-by: Matt Silverlock <[email protected]>

* Update src/content/changelog/queues/2025-03-25-pause-purge-queues.mdx

Co-authored-by: Matt Silverlock <[email protected]>

* Updated changelog with links

* Update src/content/changelog/queues/2025-03-25-pause-purge-queues.mdx

Co-authored-by: Matt Silverlock <[email protected]>

* Update queues.yaml

* Update 2025-03-25-pause-purge-queues.mdx

* Apply suggestions from code review

---------

Co-authored-by: Matt Silverlock <[email protected]>
Co-authored-by: Jun Lee <[email protected]>

Author: 3 people

src/assets/images/queues/pause-purge.png

@@ -0,0 +1,37 @@
+---
+title: New Pause & Purge APIs for Queues
+description: Queues now supports the ability to pause delivery and/or delete messages from a queue, allowing you to better manage queue backlogs.
+products:
+  - queues
+date: 2025-03-27 12:00:00 UTC
+---
+
+[Queues](/queues/) now supports the ability to pause message delivery and/or purge (delete) messages on a queue. These operations can be useful when:
+
+* Your consumer has a bug or downtime, and you want to temporarily stop messages from being processed while you fix the bug
+* You have pushed invalid messages to a queue due to a code change during development, and you want to clean up the backlog
+* Your queue has a backlog that is stale and you want to clean it up to allow new messages to be consumed
+
+To pause a queue using [Wrangler](/workers/wrangler/), run the `pause-delivery` command. Paused queues continue to receive messages. And you can easily unpause a queue using the `resume-delivery` command.
+```bash title="Pause and resume a queue"
+$ wrangler queues pause-delivery my-queue
+Pausing message delivery for queue my-queue.
+Paused message delivery for queue my-queue.
+
+$ wrangler queues resume-delivery my-queue
+Resuming message delivery for queue my-queue.
+Resumed message delivery for queue my-queue.
+```
+
+Purging a queue permanently deletes all messages in the queue. Unlike pausing, purging is an irreversible operation:
+```bash title="Purge a queue"
+$ wrangler queues purge my-queue
+✔ This operation will permanently delete all the messages in queue my-queue. Type my-queue to proceed. … my-queue
+Purged queue 'my-queue'
+```
+
+You can also do these operations using the [Queues REST API](/api/resources/queues/), or the dashboard page for a queue.
+
+![Pause and purge using the dashboard](~/assets/images/queues/pause-purge.png)
+
+This feature is available on all new and existing queues. Head over to the [pause and purge documentation](/queues/configuration/pause-purge) to learn more. And if you haven't used Cloudflare Queues before, [get started with the Cloudflare Queues guide](/queues/get-started).

src/content/changelog/queues/2025-03-25-pause-purge-queues.mdx

@@ -5,6 +5,22 @@ productLink: "/queues/"
 productArea: Developer platform
 productAreaLink: /workers/platform/changelog/platform/
 entries:
+  - publish_date: "2025-03-27"
+    title: Pause delivery and purge queues
+    description: |-
+      Queues now supports the ability to pause delivery and/or delete messages from a queue, allowing you to better manage queue backlogs.
+
+      Message delivery from a Queue to consumers can be paused / resumed. Queues continue to receive messages while paused.
+
+      Queues can be purged to permanently delete all messages currently stored in a Queue. This operation is useful while testing a new application, if a queue producer was misconfigured and is sending bad messages.
+
+      Refer to the [documentation on Pause & Purge](/queues/configuration/pause-purge/) to learn how to use both operations.
+  - publish_date: "2025-02-14"
+    title: Customize message retention period
+    description: |-
+      You can now customize a queue's message retention period, from a minimum of 60 seconds to a maximum of 14 days. Previously, it was fixed to the default of 4 days.
+
+      Refer to the [Queues confiuguration documentation](/queues/configuration/configure-queues/#queue-configuration) to learn more.
   - publish_date: "2024-09-26"
     title: Queues is GA, with higher throughput & consumer concurrency
     description: |-
@@ -13,7 +29,6 @@ entries:
       The per-queue message throughput has increased from 400 to 5,000 messages per second. This applies to new and existing queues.
 
       Maximum concurrent consumers has increased from 20 to 250. This applies to new and existing queues. Queues with no explicit limit will automatically scale to the new maximum. Review the [consumer concurrency documentation](/queues/configuration/consumer-concurrency) to learn more.
-
   - publish_date: "2024-03-26"
     title: Delay messages published to a queue
     description: |-