Skip to content

Prepare Workflow 2.4.3 dashboard read fix - #629

Merged
rmcdaniel merged 3 commits into
mainfrom
release/dashboard-243-20261006
Oct 6, 2026
Merged

rmcdaniel merged 3 commits into
mainfrom
release/dashboard-243-20261006

Conversation

@rmcdaniel

@rmcdaniel rmcdaniel commented Oct 6, 2026 •

Copy link
Copy Markdown
Member

Release Workflow 2.4.3

Prepare the exact stable package identity for the bounded dashboard read change
merged in #628, supporting durable-workflow/waterline#141. No protocol or execution
semantics change.

The underlying source passes all selected PR gates, local PHPStan and six focused
cases / 35 assertions. Its full main database, unit, coverage and Laravel gates
must pass before tagging. This PR sets the package train identity and runs the
focused bounded-read regression in the existing MySQL, PostgreSQL and MariaDB
jobs. SQLite remains covered by the ordinary unit suite. No new runner or
workflow is introduced.

The full unit gate found an existing timer fixture that used wall-clock now()
after creating its workflow logical clock. Crossing a second boundary made its
supposedly elapsed timer future-dated. Set that fixture's deadline from
WorkflowStub::now() and retain the same result/log assertions. Timer execution
semantics are unchanged. Recheck the unit gate before tagging.

Before calling the patch delivered, verify Packagist, the published package
contract and supported Laravel upgrade matrix. Run the bounded-read regression
from a fresh installed package. Waterline must opt into the new method and
preserve unknown audit counts. Server's pinned package and dashboard endpoint
need an update before service observers use the bounded path. Sample App and
Cloud pins need explicit consumer decisions. No SDK release is needed for the
embedded additive method; any service transport change will be qualified through
its owning repository.

@rmcdaniel
rmcdaniel marked this pull request as ready for review October 6, 2026 17:56
@rmcdaniel
rmcdaniel merged commit 8fcfb00 into main Oct 6, 2026
16 checks passed
@rmcdaniel
rmcdaniel deleted the release/dashboard-243-20261006 branch October 6, 2026 17:57
@rmcdaniel

rmcdaniel commented Oct 6, 2026 •

Copy link
Copy Markdown
Member Author

Workflow 2.4.3 is published from 8fcfb002de337e341ef19e601d73e9e1424e09ec,
qualified tree bd2793f4a5ec940d2612b8246ea3aa593d2a591e. Full source gates,
coverage and all supported database/Laravel cells pass in
37507390693
and 37509525043.
Packagist identity and a fresh unpatched registry consumer are verified,
including 6 bounded-read cases / 35 assertions with no skips. Merged branches
were deleted and verified absent.

Server 2.5.3
now includes that exact published dependency. Both registries and architectures
are verified at index
sha256:7c62b388802dda1922ada0a920ea8335c6a05ed3638741137cea4c8ba228bf22.
A fresh PHP SDK 2.2.1 consumer passes 13 real bounded-dashboard HTTP checks.
Published lifecycle verification
passes all 12 cells with no findings.

The bounded dashboard foundation is delivered. Waterline #141
remains open for classification filters, bounded details, complete failure
references and its five published acceptance fixtures. Sample App's coherent
observer update follows that qualification. Execution and worker semantics are
unchanged by this dashboard foundation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants