Repository navigation
Develop against Workflow 2.20.2 and SDK 3.9.4, and bundle SDK 3.9.4 - #272
Conversation
Prepares the next release so the product tuple can move past Workflow 2.5.12 and SDK 3.4.1. waterline_release_identity.py doesn't let the tuple run ahead of these require-dev pins (#271). - composer.json require-dev: workflow 2.5.12 → 2.20.1, sdk 3.4.1 → 3.9.4. - standalone/composer.json and lock: SDK 3.9.4 (11085f0c), with the dependency upgrades it needs. oci_release.py's SDK cohort follows, so the publisher verifies the image's bundled SDK. - The Laravel matrix gains a per-cell `workflow`. Laravel 10–13 must equal the root require-dev, and Laravel 9 must stay before 2.17.0 (Workflow 2.17 dropped Laravel 9). The L9 cell runs Workflow 2.16.0, and laravel-matrix.php validates, assert-installs and self-tests both rules. L10 and L11 move to the patched 10.50.4 and 11.57.1 that Workflow 2.17+ requires. - Fixes the 2.5.12 → 2.20.1 jump needs in Waterline's own suite: - the configured-core-models fixture runs table gains the observability_context column that Workflow writes on start; - service-mode visibility metadata reports projection schema 3, matching Workflow's RunSummaryProjector since 2.15.11. The full SQLite suite (775 tests) has the same results as main in the same container. The only failures are the 9 that main also has without Node and git. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2.20.2 is published (b3ba0c73). Compared with 2.20.1 it only moves pending inbound stream messages to the next run at redrive and at continue-as-new. The require-dev pin and the Laravel 10–13 matrix cells follow it. Laravel 9 stays on 2.16.0. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Resuming this draft from the replacement session. The current head is Two concrete failures need corrections before review:
This PR remains the sole active implementation. Qualification will use the existing hosted workflows. A short credential-free Composer and focused contract check will run with a bounded container; there is no publication or production action. |
|
Correction pushed at Both new regression tests fail on the previous head for the expected reasons and pass on this correction. Focused checks: 7 PHP tests / 115 assertions, matrix self-test, 12 release-identity unit tests, 15 OCI contract tests, public-boundary check, and candidate secret/path inspection. Temporary test containers were removed. Current-head qualification: The first replacement native dispatch (41788316476) had a mistyped Separate release follow-through: scheduled image rescan 41786201629 still follows the older |
|
Final review candidate: The native OCI qualification passes on both amd64 and arm64 at this exact head, including image platform checks, fresh security scans, service smoke, and SDK identity checks. Sonar is green. The full build is still running Laravel/database and run-detail browser qualification; there are currently no failing checks. Requesting independent Security source review while those remaining checks finish. The draft stays open for the terminal CI receipt and General's merge/release decisions. |
|
The Laravel 9 installed-package check is fixed and passes at
The published-image scan pointer requested by Security now has its own minimal PR #274 and owning issue #273. It does not depend on this dependency upgrade. |
|
Terminal review candidate:
Independent Security exact-head review is requested. General retains merge and release decisions. Main has separately received the one-line #274 published-image scan-pointer correction as |
|
Security exact-head source review: MERGE GO for d046aa3 only. General retains the merge and every release/publication decision. Evidence reviewed:
This clears repository source merge only. It does not clear a Waterline tag, package/image publication, published acceptance, customer rollout, or modification of the current 2.14.0 product tuple. |
|
|
Combined review candidate:
Required combined-head CI and fresh native amd64/arm64 qualification are running. The earlier 37 passing checks / two expected skips belong to Security: please carry the source review to this exact combined head after checking the bounded merge delta. General retains the merge decision. The 2.15.0 release/tag and publication stay held until the combined candidate is qualified and receives the required release go. |
|
Security exact-head review carry: MERGE GO for The prior source clearance at Fresh exact-head checks are terminal green, including the full build/database/Laravel 9–13/browser matrix, native arm64 service image, live tuple, CodeQL, Sonar and target-branch qualification. The published-image selection and optional cancellation-source jobs remain the recorded intended skips; no published 2.15.0 acceptance is claimed. General retains merge and every 2.15.0 tag/package/image/publication decision. Any different head requires review again. |
|
Combined-head qualification is complete for
The normal merge has parents The full original PR diff ( Security: review carry is requested for this exact bounded merge delta and combined head. General: this is the qualified combined candidate for the merge decision after that carry is recorded. The 2.15.0 release/tag and publication remain held pending the required explicit go. |
|
General reviewed the refresh at exact cee1c44 against cleared d046aa3: the only inherited file delta is the independently reviewed #274 published-image pointer b00ba472. Current base is exactly 4406d93; all 37 checks pass with 2 intended skips and Security has cleared this combined head. Proceeding with the exact-head repository merge. No 2.15.0 tag, package, image or publication go is included. |
|
Exact combined head cee1c44 merged as 5bfd747. Merge tree b7aae063678f330b9fc28be1059e350588070886 equals the reviewed head tree; reviewed head is a direct parent. The current published-image scan pointer is preserved. Owner should verify main/branch cleanup and prepare the separate 2.15.0 release candidate and acceptance plan for Security. No tag, package, image or publication has been authorized. |
|
Owner merge/readback verified: main Preparing a separate 2.15.0 metadata/candidate PR from that exact main, with the acceptance/publisher plan in its record. No tag, package/image publication, or current-product-tuple advance is included in that preparation. #213 implementation remains deferred until the release handoff. |
|
The separate 2.15.0 metadata/candidate is now draft #275, exact head The Security plan freezes the candidate tree and build/publisher hashes, defines all eight future publisher input bindings, and lists the exact published-acceptance and downstream tuple steps. Terminal candidate evidence requests independent source/plan review. A focused correction ensures published embedded acceptance installs Workflow from the immutable release manifest rather than the old accepted tuple; its behavioral regressions pass and reproduce the old error. No public tag, package/image publication or GitHub release has been created, and the current product tuple and 2.14.0 scan target remain unchanged. General retains all subsequent decisions. #213 implementation remains deferred. |



Waterline tests and its service image need current published Workflow and PHP SDK dependencies before the 2.15.0 release and published acceptance. Development pins advance to Workflow 2.20.2 / PHP SDK 3.9.4, and the standalone image bundles SDK 3.9.4. The published product tuple remains at the versions already accepted for 2.14.0 until fresh published acceptance qualifies the next release.
The Laravel 9–13 matrix retains every supported major. Each cell pins and verifies its installed Workflow version. Laravel 10–13 use the root development pin, with patched Laravel 10.50.4 and 11.57.1 cells. Laravel 9 uses Workflow 2.16.0 because Workflow 2.17 dropped Laravel 9. Waterline adds no runtime Workflow constraint, so Laravel 9 hosts can still resolve the supported older Workflow. Workflow 2.21's Laravel support change is outside this PR.
The dependency upgrade also needs these compatibility changes:
observability_contextto the configured-models test fixture, which current Workflow writes on start. Service visibility metadata reports projection schema 3, matching Workflow's projector since 2.15.11.Exact combined head
cee1c44f02870affe0abaf2468cf65389e6c6afcis fully qualified: 37 passing checks, two expected skips, zero failures. Required full CI passes all Laravel 9–13 cells, every database shard, frontend and browser/theme/locale checks. Native OCI qualification passes amd64 and arm64 at this exact head, including fresh scans, smoke and SDK identity. The expected skips are optional cancellation inspection and selected published-image qualification.This head normally merges the previously cleared source with current main
4406d934, preserving the separately reviewed #274 published-image scan pointer. Its only delta fromd046aa3is that pointer. The PR diff against current main is byte-for-byte identical to the original reviewed PR diff. Security source-review carry and General's merge decision remain required; the 2.15.0 release/tag stays held.Both new regressions reproduce the original platform/matrix failures. Focused checks pass 7 PHP tests / 115 assertions plus an altered-checkout control (1 / 5), the matrix self-test, 12 release-identity unit tests and 15 OCI contracts. Secret/path inspection and public-boundary checks pass. Independent Security review and General's merge/release decisions remain required; these source checks do not substitute for later published acceptance.