Adopt published deterministic workflow clock fix - #91
Conversation
|
The focused embedded and Laravel service-mode checks pass against MySQL: 8 tests, 44 assertions with the published Workflow 2.0.14 package. The first CI run stopped before application tests because I had missed the checked-in qualified artifact tuple when updating composer.lock. The tuple now agrees with the lock; normal CI is rerunning. No application or CI behavior was changed to bypass that validation. |
|
All checks now pass, including application tests, Compose workflows, PHP/Python/Rust smoke and the prepared development image. Server 2.3.12 is publishing from durable-workflow/server#163; once its exact image is verified I will align the Server entry here as well, so the sample does not retain an image with the old engine. This remains the same dependency-update PR. |
|
Merged at b830288 after every final-head check passed, including the Codespaces image, PHP/Python/Rust workflow execution, Compose workflows and PHP 8.4/8.5 application tests. Main publication/verification is now running to promote the prepared image for new Codespaces. |
|
Main publication is complete: both amd64 and arm64 prepared images passed credential-free published-image qualification and the main channel was published. All main checks are green. Workflow 2.0.14 and Server 2.3.12 are now the checked-in Sample App tuple. Publication run. |
Change
Adopt published Workflow 2.0.14 for embedded execution and Server 2.3.12 for service mode. Update composer.lock and the existing qualified artifact tuple together. No SDK, Waterline, framework or other dependency update.
The engine fix prevents deadline arithmetic from mutating deterministic workflow time. Upstream: durable-workflow/workflow#512 and durable-workflow/server#163; delivery tracking: durable-workflow/workflow#511.
Validation
No new performance or SLA claim is made.