Repository navigation
Prepare Workflow 2.10.0 activity lease release metadata - #885
Conversation
Fresh main failure; hold 2.10.0 taggingExact merged main The exact retained logs were read using the existing host-interface path. The old fixture manually creates a running execution and leased task without an attempt row/current-attempt identity. The new lease-loss settlement requires the original generation. Before changing any expectation, qualify a genuinely claimed attempt through the watchdog and a complementary incomplete-projection refusal control. This is not yet proof of a production regression or a passing corrected fixture. No rerun, timeout relaxation or rescued original is claimed. Draft release-metadata #885 ( |
|
Workflow 2.10.0 published componentRelease PR #885 is merged at Immutable release 2.10.0 is published. Packagist resolves exact This releases original activity claim authority/recovery and the optional bridge role. #878 remains open for embedded automatic inline maintenance, final PHP/Rust SDK publication, Server adoption and actual published long-activity/worker-loss acceptance. It is not a claim that callbacks now maintain themselves, or that an abandoned callback physically stopped. Server #585's urgent select-cancellation patch deliberately keeps its qualified Core 2.9.0 pin. The separately prepared activity-lease Server source will adopt published 2.10.0 in its own qualified dependency/consumer window. No native/shared/frozen reference or catalog adoption follows from this package release. |



Prepare compatible Workflow 2.10.0
Based on merged #879 and its #886 watchdog coverage follow-through, exact source main
3e3add8693c624195ff6818985c7bb10cc4920fa/ treea84d4f29d6c4491828782f30119c30e3b5e0264e. The implementation adds an optional runtime lease-renewal contract without changing existing custom ActivityTaskBridge implementations, plus recorded lease-loss/departure recovery and original workflow-deadline fences. A compatible minor release makes that contract available to the coordinated Server and SDK delivery for #878.This PR changes only the product-train metadata to 2.10.0 and the changelog. Dependencies, package references, runtime, schemas and native/shared/frozen files are unchanged. The library tracks no composer.lock. The changelog also corrects the prior tracing entry's stale 2.8.0/Unreleased heading to actual published 2.9.0 (October 21), and records actual 2.8.0 (October 20); both dates/features were read from immutable release records.
Updated ancestry-only candidate is
54269101ce546c092320fbd74edd79ba8dc7893a, tree3de4f2a76e315709d592b0d2f4270bd8a520a91b. Strict Composer validation passed for the unchanged metadata on predecessor3fd8bcad; its short-lived UID-1000/network-disabled PHP container is removed. Diff review confirms this candidate still differs from source main only in composer.json and CHANGELOG.md. Production source/resource bytes match the new merged main exactly. New whole-head normal gates are required; no predecessor pass is borrowed.Tagging is held on fresh-main and updated candidate qualification. Original source-main build
39563295508failed the same old watchdog fixture on MySQL shard 2 and PostgreSQL shard 3. Those failed originals remain failed. Follow-through #88694589cf0adds actual original-claim retry/history/idempotency coverage and refusal to invent a missing attempt, with no production change. Local complete PostgreSQL file passes 128 tests / 1,736 assertions, and fresh MySQL watchdog selection passes 12 / 175; its broader OOM-failed MySQL original is not rescued. Every normal #886 gate and Sonar passed before protected merge at3e3add86, preserving exact reviewed treea84d4f29. Independent full fresh-main checks and this updated metadata head must now qualify.The old metadata candidate's passing normal gates do not override the new whole-head requirement. Normal immutable package/registry verification and installed consumers remain required after tagging. No earlier tree's pass is transferred. No release or complete #878 acceptance is claimed now.
Automatic maintenance for PHP/embedded inline callbacks and the genuine installed six-minute/killed-worker cohort remain tracked in #878. This release preparation does not close that P1.