Skip to content

Put keyed reminders in the release they ship in #9

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
cardmagic merged 1 commit into from
Aug 17, 2026
Merged

Put keyed reminders in the release they ship in #9

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
5 changes: 1 addition & 4 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -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
Expand All @@ -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.
Expand Down