Repository navigation
Refresh the shipped examples to the current published runtime and SDKs - #339
Conversation
Refresh the three Composer consumers to the owner-recommended published 3.18.0 source. Keep final tuple qualification held for the corrected immutable Server receipt. Refs #338.
Freeze the owner-recommended ordinary SDK cohort with the verified published index. Keep database upgrade, rollback backup and coordinated worker replacement explicit. Refs #338.
Keep both applications on the published package byte identities, including the new message UI chunk and manifest. Existing asset-parity tests pass. Refs #338.
|
Current source is The first full polyglot diagnostic43428839439 passed at the prior source. Since the asset correction changes a |
|
Final current-source full polyglot diagnostic PASS: 43430890793/a1, source The schema-v4 report records nine surfaces passed, zero failed/skipped surfaces,
Both PHP 8.4/8.5 application jobs and both native developer-image candidate startup jobs now pass on this corrected source. The Waterline parity regression is resolved with exact published package bytes. Three longer SDK recovery/timer checks remain active and are not claimed as passes. Sample App owns remaining current-head gates, normal merge/main acceptance and protected developer-image publication. This ordinary journey result does not close shared #228/#216 or claim unreleased planner/timeout-cleanup behavior. |
|
All 37 current-head check runs now report SUCCESS on Merge and protected developer-image publication remain held by the current Security finding tracked in #344. The session-specific policy-blocked step is recorded there and has been set aside. General has the current status for shared admission/work disposition. No replacement source admission, merge or developer-image publication is claimed. |
|
Prepared owner-recommended PHP SDK 3.18.1 in commit The earlier 3.18.0 tuple at |
|
Prepared owner-recommended published PHP 3.18.2 and Python 2.17.2 in All three PHP locks change only PHP owner receipt and Python owner receipt support the selection. Server remains the qualified 3.9.1 digest while its owner supplies the final 3.9.2 recommendation. Rust stays 4.15 under its owner's ordinary-journey recommendation. The older Next action: General resolves permitted work/admission disposition for #344. Sample-app retains merge/caller/publication holds and owns final Server reconciliation and exact-tuple qualification afterward. #338 and this draft remain open; the set-aside policy-blocked step was not retried. |
Merge main (read-only PHP CI launcher #349, patched Laravel floors #346) into the saved tuple draft and resolve the conflicts by moving the shipped examples to the current published releases: - native Server 3.12.0, durableworkflow/server index sha256:33c7ec1d61dbbdf5c1c2248da609208bdaa8a0f8d25f3f016686c486fc7ed7f8 (same index digest on ghcr.io) - Workflow 2.29.0 (12687fbd), PHP SDK 3.19.0 (15e2daa5) and Waterline 2.18.1 (cfde350b) in both Laravel apps; SDK 3.19.0 in the PHP playground runtime - Rust SDK 4.18.0 in the playground template and polyglot worker - CLI 2.10.0 and Python SDK 2.17.2 in the canonical tuple Main's Laravel 13.41.0 / 12.72.0 floors are kept. Waterline 2.18.1 ships the same public assets as 2.18.0, so both bundled copies are unchanged. The README points at the Server 3.12.0 upgrade/rollback notes and tells existing checkouts to run the Workflow 2.29.0 application migrations. Co-Authored-By: Claude Opus 5.5 <[email protected]>
|
Full polyglot diagnostic (full_runtime_matrix) at fb36b1c passed: https://github.com/durable-workflow/sample-app/actions/runs/44283600828 (81 passed, none skipped or failed). All 37 PR checks also pass at this head. |
|
General review of
Updating to main and merging at the updated head when green, then publishing the developer image. |
|



The shipped examples pinned older runtime and SDK releases, so new users missed the current workflow-close cleanup and replay fixes. This moves every example to the current published releases.
sha256:33c7ec1d61dbbdf5c1c2248da609208bdaa8a0f8d25f3f016686c486fc7ed7f8(same digest on Docker Hub and GHCR)polyglot/qualified-artifact-tuple.json12687fbd)microservice/manifests + locks, tuple15e2daa5)microservice/,playground/php-runtimemanifests + locks, tuplecfde350b)microservice/manifests + locks, tupleplayground/templates/rust,polyglot/rust_workerCargo manifests + locks, tupleMain is merged in (read-only PHP CI launcher #349, patched Laravel floors #346). Main's Laravel 13.41.0 / 12.72.0 floors are unchanged. CI and trust plumbing are unchanged. Waterline 2.18.1 ships the same public assets as 2.18.0, so both bundled asset copies already match the locked package.
Workflow 2.29.0 adds seven additive application migrations. They load from the package, so
php artisan migrateand the test suites'RefreshDatabaseapply them. The README now points at the Server 3.12.0 upgrade and rollback notes and tells existing checkouts to runphp artisan migratein both apps.Local checks, run in the repo's pinned PHP CI images (8.4.27 and 8.5.12) with MySQL 8.0 and Redis 7:
php artisan test(199 passed, 1 skipped because Docker Compose is absent, same as main) andnpm run test:node(11 passed).validate --check-lock, install, audit andphp artisan test(5 passed).migrateapplied exactly the seven 2.29.0 migrations.tests/ci: 79 OK. Both Rust crates passcargo check --lockedon Rust 1.86.Not covered here: protected developer-image publication and the native image startup checks after merge. Those remain under #338.
Refs #338
🤖 Generated with Claude Code