Repository navigation
-
Security fix: webhook
tokenauthentication with no token configured
accepted requests that omitted the token header. It now refuses every
request with503and logs a warning naming the missing setting.signature
authentication with no secret configured, which failed with a type error, now
refuses the same way. Use thenonemethod for webhooks without
authentication. Deployments usingnone, a custom authenticator, or a
configured token or secret are unaffected. -
Workflow code can read the schedule fire that started its run with
$this->scheduleOrigin()(durable-workflow/.github#243). It returns a
Workflow\V2\Support\ScheduleOriginwithscheduleId,occurrenceTime
andtriggerNumber, ornullfor a run no schedule started.
occurrenceTimeis the time the scheduler evaluated: the jittered fire
time for a tick, the enumerated time for a backfill. It isnullfor a
manual trigger. The value comes from the run'sScheduleTriggeredhistory
event, which is committed with the run's start. So it is available on the
first workflow task and identical on replay. -
A scheduled run's continue-as-new successor now records its predecessor's
ScheduleTriggeredevent right after its start, as native Server does
(server#1143). The successor keeps the same schedule origin. Runs not
started by a schedule record nothing new, and existing histories replay
unchanged. -
Rolling back the compensation-scope migration now refuses while the ledger
holds any scope (#1063). In 2.29.0 and 2.29.1,migrate:rollbackdropped
those tables, discarding unresolved obligations and the released tombstones
that keep old generations and request keys from being accepted again. Empty
ledgers still roll back. To downgrade with retained scopes, restore a
database backup taken before the upgrade. Two new replay fixtures pin the
2.29 histories of a completed parent with a child participant and of
in-origin Saga cleanup after a lost forward result. -
CI now installs published 2.28.1 into a new Laravel application, upgrades
it and checks retained compensation scopes (#1063). The job covers recovery
after the origin run closes and schema rollback with an empty and a
populated ledger. It also checks a package downgrade that keeps the ledger,
followed by an upgrade that recovers it. It runs on pull requests that
change migrations or compensation code, and on stable release tags against
the published package.docs/compensation-scopes.mddescribes the rollback
and downgrade behavior it checks. -
Query-state replay (queries and
WorkflowReplayer) now delivers a recorded
cooperative cancellation to an activity, timer, signal or condition call that
never opened, at the same position the executor used (#1069). Previously a
cancellation that arrived before such a wait opened made query-state replay
report a history shape mismatch, though the run itself replayed and completed
correctly. A new replay fixture pins the signal-wait history. -
The experimental provider state-machine example's common payment-first
checkout can opt into one partial-stock policy (fulfill-partial,
wait-completeorcancel-all) through trusted bootstrap (#1069). The
policy is part of the business grant; workflow arguments and signals cannot
change it. The example's unit refund no longer records a confirmed refund as
unknown because of an over-long evidence reference. See
examples/provider-state-machines/README.md.
No new migrations. Upgrading from 2.29.x needs no schema step.