From d1da79bc1f5be775e9d0a10eaa02e756b04984ec Mon Sep 17 00:00:00 2001 From: Ruben Fiszel Date: Tue, 4 Aug 2026 06:46:33 +0000 Subject: [PATCH] docs: name the release this actually ships in --- docs/schedule-email-removal.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/schedule-email-removal.md b/docs/schedule-email-removal.md index afd874c8bd..b23860d6d2 100644 --- a/docs/schedule-email-removal.md +++ b/docs/schedule-email-removal.md @@ -2,11 +2,11 @@ A schedule's identity is its `permissioned_as`; the address beside it is a function of that principal. `schedule.email` is no longer read for the identity, but it is still written, because -workers before **1.777** select it in `get_schedule_opt` — inside the same transaction as the job +workers before **1.779** select it in `get_schedule_opt` — inside the same transaction as the job completion, so a missing column rolls that completion back and the occurrence runs again. That is the failure to keep in mind throughout: not a wrong address, a schedule that runs twice. -The column can go once no worker older than 1.777 can be live, in practice once +The column can go once no worker older than 1.779 can be live, in practice once `MIN_KEEP_ALIVE_VERSION` (`windmill-common/src/min_version.rs`) has passed it. There is no `MIN_VERSION_*` constant for this and it does not need one: those gate behavior at runtime, and nothing here does — the write is unconditional, so no worker meets the column's absence until