Repository navigation
Adopt the fixed embedded activity build routing - #274
Merged
Merged
Conversation
|
Member
Author
|
Published consumer acceptance is complete for this Sample change.
The first candidate's missed nested-lock seed failure remains failed. Initial manual registry readers also failed before correcting redirect handling; these verifier failures are separate from the final anonymous registry result. This delivers the embedded Sample consumer, not a replacement Server release or a new published Server worker-loss qualification. |
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
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.



Changes
Refs durable-workflow/workflow#908. Update the embedded runtime from Workflow
2.9.0 to published 2.11.2 in both normal Composer locks and the embedded artifact tuple. This
includes the rolling-deployment fix that lets versioned workers claim an
unpinned activity without weakening pinned-build isolation.
The Server remains 2.10.0 with its separately declared Core 2.9.0 component.
All SDK, Waterline and CLI selections and all other locked packages are
unchanged. No Server image or shared/frozen cohort is retupled.
Validation
Normal Composer 2.10.3 resolution and installation pass on PHP 8.5.12 using
the reviewed trust bundle. Full lock comparison finds exactly one changed
package. The loaded Core is 2.11.2 /
a730773a, and the activity bridge hashmatches the published release. Manifest validation, locked audit, installed
artifact graph and installed AI documentation contract pass.
Local application qualification is incomplete: the simple workflow test hits
the existing MySQL-only shared connection in the SQLite-only tool image. A
broader Unit attempt also fails development-image requirements (image-baked
SDK, Git worktree metadata, pip/Node/Docker and runtime inputs). These attempts
are retained as failed runner observations, not reported as passes or package
defects. Normal CI's real MySQL application suites and native image gates must
qualify this exact candidate before merge. No browser or published-image
acceptance is claimed by the local package check.
First hosted candidate f01a92c failed image job 120269025137 in run
39909529715: its unchanged image guard found Core 2.9.0 in the microservice
seed while the embedded tuple required 2.11.2. General missed that second lock.
Corrected 95e3640 updates it through normal Composer resolution; both lock
comparisons find only Core changed and strict validation/audit pass. The guard
and all other packages are unchanged. Fresh whole-tree checks are required.
Six still-live superseded Sample runs were cancelled; their cancelled states
and the original failed image remain explicit, with no transferred passes.
No Server/native original was cancelled.
Exact corrected candidate
95e3640/ whole14b93ad8now passes all 32normal checks, including both real MySQL PHP application matrices, both
architecture workflow smokes, the candidate development-image build, all
published SDK consumer scenarios, CodeQL and Sonar. No prior-head pass is
carried across. The first failed image and cancelled superseded runs remain
explicit. Independent main checks and published-image qualification follow.