Update embedded Workflow to published 2.0.10 - #85
Merged
Conversation
4 tasks
rmcdaniel
marked this pull request as ready for review
September 9, 2026 18:09
Member
Author
|
Downstream delivery verified on main 0b21698: application CI, Compose journeys and PHP/Python/Rust smoke all pass. The prepared development image was published and qualified anonymously on both linux/amd64 and linux/arm64, then promoted to the main channel with both public registry indexes verified: https://github.com/durable-workflow/sample-app/actions/runs/34387279236 . The installed embedded Workflow lockfile and declared tuple are 2.0.10; unchanged tuple components are not being described as newly upgraded. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The committed lockfile still installed Workflow 2.0.2 despite the compatible
^2.0requirement. Update only that package to published 2.0.10 so a freshcomposer installincludes the released cleanup/replay, concurrency, timeout and MariaDB fixes.Composer dependency resolution, audit, metadata validation and diff checks pass. Runtime tests and fresh-install verification are pending; this is not a claim of completed application conformance. No SDK/API change or unrelated dependency update.
Release follow-through: durable-workflow/workflow#500; companion Server consumer update is tracked in its own PR.