Problem
Server 2.0.0-beta.15 is publicly verified, while the other current components remain on 2.0.0-beta.14. The Server image is immutable and embeds Workflow 2.0.0-beta.14 with a beta.14 client compatibility window. Public artifact metadata therefore cannot truthfully present one synchronized current 2.0 train, and exact-current quickstart validation stops before execution.
Required outcome
Publish one coherent 2.0.0-beta.16 successor across Workflow, Waterline, Server, CLI, and the PHP, Python, and Rust SDKs. Bind every package, image, executable, dependency, compatibility declaration, and public release to its exact protected source. Update the sample application and versioned documentation to the same tuple while stable 1.x remains the unversioned default.
The Server beta.16 image must consume Workflow beta.16 and advertise the beta.16 client window. Waterline beta.16 must consume the beta.16 Workflow and PHP SDK packages and publish both its Composer package and multi-architecture service image. SDK and CLI metadata must name beta.16 as the product train and supported Server release. Do not add compatibility shims for earlier 2.0 prereleases.
Completion evidence
- All seven release surfaces resolve publicly at 2.0.0-beta.16 with immutable source identity and registry verification.
- The Server and Waterline images expose the expected source labels and required architectures.
- The public sample application and versioned docs use only the beta.16 tuple; stable 1.x remains the default docs line.
- The quickstart executes its PHP, Python, Rust, operator, and embedded Laravel scenarios to workflow completion from published artifacts.
- A fresh full conformance wave records the beta.16 tuple without stale or mixed-version evidence.
- Release recovery resolves the immutable beta.16 plan and performs credential-free no-op decisions for already-correct public artifacts.
Required source targets
durable-workflow/.github@main
durable-workflow/cli@main
durable-workflow/durable-workflow.github.io@main
durable-workflow/sample-app@main
durable-workflow/sdk-php@main
durable-workflow/sdk-python@main
durable-workflow/sdk-rust@main
durable-workflow/server@main
durable-workflow/waterline@v2
durable-workflow/workflow@v2
Problem
Server 2.0.0-beta.15 is publicly verified, while the other current components remain on 2.0.0-beta.14. The Server image is immutable and embeds Workflow 2.0.0-beta.14 with a beta.14 client compatibility window. Public artifact metadata therefore cannot truthfully present one synchronized current 2.0 train, and exact-current quickstart validation stops before execution.
Required outcome
Publish one coherent 2.0.0-beta.16 successor across Workflow, Waterline, Server, CLI, and the PHP, Python, and Rust SDKs. Bind every package, image, executable, dependency, compatibility declaration, and public release to its exact protected source. Update the sample application and versioned documentation to the same tuple while stable 1.x remains the unversioned default.
The Server beta.16 image must consume Workflow beta.16 and advertise the beta.16 client window. Waterline beta.16 must consume the beta.16 Workflow and PHP SDK packages and publish both its Composer package and multi-architecture service image. SDK and CLI metadata must name beta.16 as the product train and supported Server release. Do not add compatibility shims for earlier 2.0 prereleases.
Completion evidence
Required source targets
durable-workflow/.github@main
durable-workflow/cli@main
durable-workflow/durable-workflow.github.io@main
durable-workflow/sample-app@main
durable-workflow/sdk-php@main
durable-workflow/sdk-python@main
durable-workflow/sdk-rust@main
durable-workflow/server@main
durable-workflow/waterline@v2
durable-workflow/workflow@v2