Repository navigation
PHP SDK 3.11.0 keeps a condition wait's first deadline across false wakes when Native Server 3.3.0 advertises condition_wait_occurrence_deadline. New top-level waits use an occurrence deadline; recorded legacy chains keep their existing behavior. Grouped condition waits do not opt in yet (#278).
Upgrade every worker on a queue together. On an older Server, upgrade all workers to 3.11 before upgrading the Server. On a Server that already advertises the capability, drain or stop every older worker, including standby and autoscaling pools, before any 3.11 worker consumes the queue. Once an anchored chain exists, do not downgrade that queue's workers below 3.11. An older worker's reopen is refused and the worker can exit; a 3.11 worker can resume the run.
If the Server loses the capability, an existing anchored chain leaves its task claim without completing or failing it. The claim ends through its configured lease or another ordinary authority transition; a capable Server can resume the run. No fixed retry interval, in-place SQLite Server rollback or automatic mixed-chain repair is promised.
The bare SDK retains PHP ^8.1; Laravel bridge constraints, worker protocol 1.20 and control plane 2 are unchanged. See the upgrade guide.
The shipped anchored qualifier records the actual replay input and accepted completions, binds fresh Native exports, and retains raw export/witness files for C1, repeated wakes and separate occurrence budgets. Candidate qualification passed these three cases on Native 3.3.0; published-package follow-through is recorded in #269.