From 5d17a5a3704a6f93d22dfa12bb4e65e2f68c4568 Mon Sep 17 00:00:00 2001 From: Gael Ollivier Date: Tue, 13 Jan 2026 08:25:36 -0800 Subject: [PATCH] Fix typo in Breaking Change README Fixed the example in the "Breaking Change" docs --- README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index a64c1159..fd4b35ac 100644 --- a/README.md +++ b/README.md @@ -508,7 +508,7 @@ which got updated to: ```ruby class MyWorkflow < Temporal::Workflow def execute - Activity1.execute! + ActivityOld1.execute! if workflow.has_release?(:fix_1) ActivityNew1.execute! @@ -519,7 +519,7 @@ class MyWorkflow < Temporal::Workflow if workflow.has_release?(:fix_1) ActivityNew2.execute! else - ActivityOld.execute! + ActivityOld2.execute! end if workflow.has_release?(:fix_2) @@ -534,7 +534,7 @@ end If the release got deployed while the original workflow was waiting on a timer, `ActivityNew1` and `ActivityNew2` won't get executed, because they are part of the same change (same release_name), however `ActivityNew3` will get executed, since the release wasn't yet checked at the time. And for -every new execution of the workflow — all new activities will get executed, while `ActivityOld` will +every new execution of the workflow — all new activities will get executed, while `ActivityOld2` will not. Later on you can clean it up and drop all the checks if you don't have any older workflows running