Skip to content

Prevent independent PHP SDK releases from breaking the current Waterline train #83

Description

@rmcdaniel

Problem

Waterline publishes an exact Composer dependency on the PHP SDK. When PHP SDK 2.0.0-rc.7 was published while Waterline 2.0.0-rc.9 still required 2.0.0-rc.6, a clean install of the exact-current Laravel tuple could not resolve. Waterline 2.0.0-rc.10 repairs that instance, but the repair reached source completion before the deployed docs tuple and five-scenario public quickstart had advanced; the 2.0.0-rc.10 release docs audit consequently failed.

This is a recurring release-coordination defect: another independently published PHP SDK prerelease can reproduce the same gap without changing runtime compatibility.

Acceptance criteria

  • Exact-current tuple qualification checks Composer satisfiability across Waterline, Workflow, and the PHP SDK before claiming the tuple is installable.
  • A PHP SDK prerelease that conflicts with Waterline’s exact dependency automatically routes a sequential Waterline prerelease and all required public artifacts, or keeps the compatibility repair incomplete until that successor exists. Historical prereleases remain immutable and no cross-prerelease compatibility shim is added.
  • Waterline release completion requires the source-bound GitHub release, Packagist package, and container image, the deployed docs artifact tuple, and a passing five-scenario exact-current quickstart including embedded Laravel.
  • Regression evidence simulates an SDK-only advance and proves source-only CI cannot mark the compatibility repair complete while public tuple evidence is stale or unresolvable.
  • One real post-fix PHP SDK/Waterline release sequence completes without an exact-current install gap.

Delete when

Delete when the coordinated release gate and regression evidence are landed, and a real successor sequence proves the current Waterline tuple remains installable through docs publication and all five quickstart scenarios.

Required source targets

durable-workflow/.github@main
durable-workflow/durable-workflow.github.io@main
durable-workflow/sdk-php@main
durable-workflow/waterline@v2

Metadata

Metadata

Assignees

No one assigned

    Labels

    authority:githubGitHub is the authoritative lifecycle record for this workbeta:compatibleMay be completed without changing the frozen beta contractkind:cross-repositoryWork spans more than one public repositorypriority:P2Normal-priority product workrepo:github-control-planeOwned by the public organization control planestatus:readyReady for implementation

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions