From f3a50964734035fd0f454e2ba344544a7d60a85b Mon Sep 17 00:00:00 2001 From: Lucas Carlson Date: Mon, 17 Aug 2026 10:14:57 -0700 Subject: [PATCH] Put keyed reminders in the release they ship in 0.13.2 has a section and a version but was never published, so the keyed reminder entry sat under Unreleased above a release that had not happened. Anyone reading the changelog would have taken 0.13.2 for shipped and the feature for waiting on a later one. Folds the entry into 0.13.2 and dates it for the day it goes out. --- CHANGELOG.md | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 3f0f98a..9c29d53 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,6 +1,6 @@ # Changelog -## Unreleased +## 0.13.2 - 2026-08-17 - Accept a `key` on `schedule`, naming a reminder for the item it is waiting on rather than for its operation, so one actor can hold an alarm per queued @@ -10,9 +10,6 @@ `message_operation` column to the reminders table, left null on existing rows. The composed name is bounded by the 255 characters MySQL holds it in, checked on the name rather than the key alone. - -## 0.13.2 - 2026-08-16 - - Add an authorized `runtime.administration.processes()` query for inspecting live and stale process rows through the runtime's database adapter. - Document rolling-deployment overlap as a reason for the polling-only warning.