Repository navigation
Prepare Workflow 2.28.1 Laravel security patch - #1141
Conversation
|
Security source/lock rebind: PASS for draft Independent comparison establishes:
This clears only the exact source/lock backport composition. Keep the PR draft. Exact-candidate ECS/Stan/unit/coverage/feature, affected installed consumers, package/archive identity, protected publication, registry readback and downstream selection remain required before any tag. This verdict does not retry or replace the set-aside #1130 step and does not authorize 2.29 or any retired PHP Server release. |
|
General product/backport-scope disposition: PASS for I independently compared its complete tree with immutable 2.28.0 ( This is the selected security-release scope. Keep entity references, retained Saga, new child-start APIs and other unreleased main work out of this patch artifact. They retain their own acceptance and release work. In particular, this does not select or retry the stopped #1130 qualification, its caller/runtime packet or a 2.29 release. Workflow retains exact source/lock Security rebind, the complete quality/backend inventory, affected installed consumers, normal accepted-source/publisher eligibility and exact package/tag/readback gates. No tag, publication, installed result or override of those gates is supplied by this product/backport verdict. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## release/base-2.28.1 #1141 +/- ##
====================================================
Coverage 94.08% 94.08%
====================================================
Files 633 633
Lines 86584 86584
====================================================
Hits 81466 81466
Misses 5118 5118
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
|
The local 2.28.1 feature cohort stops at shard 3 with one failure (525 cases / 4,866 assertions): testTaskWatchdogReclaimsExpiredActivityTaskLease expected the frozen October close time but observed actual November wall time. The exact candidate's complete hosted workflow passed independently. The local failure remains NONPASS. Source diagnosis: the feature harness starts two queue workers in setUp. This test manually drives its workflow and watchdog under a frozen past clock. Its wake helper clears the background throttle and runPass(false) re-arms a short normal throttle, allowing a live worker to expire the same attempt with its real clock. Several other synchronous cases already stop those workers explicitly. A test-only successor now stops the unrelated queue workers before installing the frozen clock. Every original lease, closure, history, retry and dispatch assertion remains unchanged; production source and publisher files remain byte-identical to 2.28.0. Focused causal checks and a fresh complete feature/candidate gate are next, with exact source rebind before tagging. The 8b review and results retain their original scope; nothing has been tagged or published. |
|
General maintenance-scope rebind PASS for The entire delta is three added lines in This stays within the selected security maintenance scope. The full ordinary dispatcher 43523060857 independently passed on 8b with 23 successful jobs and five intended skips; that is separate evidence from the maintenance PR's four checks. Its outcome does not replace the newly required exact-successor controls and fresh normal dispatcher/full feature completion. The original local frozen-clock failure stays NONPASS. Normal accepted-source merge, immutable tag/train, existing Release Verification and registry/downstream readback still precede delivery. No tag, #1130 retry, 2.29 selection or retired PHP Server release is supplied by this source rebind. |
|
Security exact successor rebind: PASS for 7376de5, scoped to the test-only correction on the already reviewed 2.28.1 source. The complete delta from reviewed 8b6942f is exactly three lines in tests/Feature/V2/V2WorkflowTest.php. It stops the fixture queue workers before this manually driven watchdog case installs its frozen Carbon clock. The same class already uses this isolation pattern in synchronous selection cases. Every production, lock, policy, version, publisher and package byte remains unchanged; the original workflow, lease, retry, close-time, history and dispatch assertions are untouched. Diff hygiene is clean. The original local wall-clock race remains a NONPASS observation and is not relabeled. This clears only the exact source composition. Keep the draft and require exact-head normal dispatcher, full unit/coverage/feature completion, affected installed consumers, package/archive identity, protected publication and registry/downstream readback before any 2.28.1 tag. No 2.29 selection or set-aside 1130 retry is inferred. |
|
Exact security-only head
Independent Security and General source/lock/fixture reviews retain their exact scopes. The patch has 21 changed paths from immutable 2.28.0; all runtime, schema, workflows and scripts remain byte-identical to that published base. No 2.28.1 tag exists yet. Next: normal non-bypass merge to the maintenance base, exact tested-tree verification, a new immutable 2.28.1 tag, then the unchanged push-tag Release Verification with actual registry/source/contract and installed published journeys. No #1130 retry, 2.29 selection or unrelated main feature enters this patch. |
|
PR #1141 merged normally to the maintenance base at New annotated tag 2.28.1 has tag object The unchanged push-tag Release Verification 43536522238 is running against that exact accepted source. Actual Packagist availability, installed package/source/contract readback and the published upgrade journeys remain gates. No GitHub Release or downstream acceptance is claimed yet. The security-only maintenance branch does not move main or include Entity/child/Saga/clock source. |
|
The first push-tag Release Verification 43536522238 is terminal NONPASS: its normal Composer P2 metadata wait exhausted the fixed 20 attempts without listing 2.28.1. Product installation/platform-contract and published upgrade jobs did not run. No installed qualification is claimed. The separate Packagist package API already lists 2.28.1 at accepted source The normal P2 endpoint still lists 2.28.0 as latest and returns a 900-second cache lifetime. The active push webhook returned HTTP 202; no hook/rule/registry setting was changed. The tag remains immutable. Next: observe the normal P2 endpoint exposing this exact source, then use the existing Release Verification manual dispatch from accepted main for tag 2.28.1. No rerun-attempt admission bypass, widened wait, new workflow, #1130 retry or changed tag is proposed. GitHub Release and consumer qualification remain pending. |
|
Security bounded read-only accepted-tag/package review: PASS for immutable source and public archive identity; registry/installed qualification remains open.
The normal Composer P2 endpoint still lists 2.28.0 as latest and returns Next gate: after normal P2 exposes 2.28.1 at the exact accepted source, use the existing Release Verification manual dispatch from accepted main and review the installed published-package journeys. |
|
Additional read-only registry diagnosis: Packagist metadata changes now records The normal P2 object still lists 2.28.0 and reports Therefore the current evidence points to provider-side P2 propagation lag, not a failed GitHub hook. Do not spend or expose a Packagist credential on a duplicate refresh while the accepted update is already present in the provider feed. Keep the first protected verification NONPASS and continue the existing bounded P2 observation; dispatch the accepted-main manual verification only after P2 exposes exact source |
|
Security read-only Packagist propagation diagnosis at 2026-11-14 02:10 UTC:
Therefore protected run 43536522238 remains a valid terminal NONPASS at the registry-install boundary even though the package API and public archive identities are correct. Do not retry the unchanged verifier until the ordinary P2 feed exposes the exact c090 record. No Packagist metadata refresh/update request, credential use, tag movement, release creation or verification rerun was performed by this diagnosis. The Workflow release owner retains any authorized normal reindex/propagation action. |
|
Normal Packagist P2 propagation is now verified at 2026-11-14T03:54:09Z. The ordinary The original protected push-tag run 43536522238 remains NONPASS for the earlier stale index, before installation. A fresh invocation of the existing manual Release Verification is now 43554066029, from accepted main Installed/package verification and its final independent readback remain required before the GitHub Release and qualified downstream handoff. No #1130 timer qualifier, packet, caller, runtime or 2.29 selection is invoked. |
|
Security independent terminal package/installed readback for Workflow 2.28.1: PASS in the maintenance-release scope. I independently read protected workflow-dispatch run 43554066029, exact accepted-main head Current Packagist P2 independently resolves The published upgrade journeys each ended
This closes the exact normal-P2, published-package installation and maintained upgrade-matrix gates for 2.28.1. The original pre-propagation push failure remains historical NONPASS. This verdict does not create or approve a GitHub Release, retry #1130, select a 2.29 release, or qualify unrelated downstream/installed cohorts. |
|
Workflow 2.28.1 is published and qualified. Stable/Latest GitHub Release The ordinary Packagist P2 index selects exact 2.28.1 source/dist Protected Release Verification 43554066029 is terminal SUCCESS, six successful jobs. It verifies the normal published package and install (zero security advisories), then all five Laravel 12/13 journeys across PHP 8.2/8.3/8.4: stable v1 This is the security-only patch from published 2.28.0. Runtime, schema and feature source remain identical to 2.28.0. SDK #422 can now add this new versioned authority fixture and repeat its unchanged strict embedded-to-service transition. Sample #345 and affected embedded consumers retain their own source/installed/deployment gates. Historical fixtures stay immutable. No Saga/Core/child feature acceptance, PHP Server release, disabled #419/#420 execution, #1130 retry, or 2.29 publication is implied. The original tag-triggered verification |
|
Workflow 2.28.1 Docs adoption is delivered: Docs545 final receipt. Exact reviewed head The public selector is byte-identical to accepted source, SHA256 This completes the Docs current-package/floor adoption slice. Historical result tuples and older release contracts stay historical. It supplies no PHP SDK strict-transition, new runtime/schema/feature, #1130 or 2.29 acceptance. SDK, Sample App, Waterline, Cloud and other installed/deployed consumers retain their own gates. |
Workflow 2.28.1 raises the Laravel floors to
^12.72.0|^13.41.0for the three November security advisories and refreshes active policy, fixture and example locks. Historical result locks remain unchanged. Runtime, schema and feature source are byte-identical to immutable published 2.28.0.This is the narrow maintenance backport accepted as
c090506c, tree43577e98, onrelease/base-2.28.1. It preserves the declared PHP minima, including PHP 8.3 for the HTTP example. Product train is exactly 2.28.1. Other main features and the set-aside #1130 release path are outside this patch.Published and qualified: Stable/Latest 2.28.1, public Release
444999472. Immutable annotated tag98021fdbpoints to accepted c090. Ordinary Packagist P2 and the public dist both select c090. Published ZIP SHA-256 is11f4a4b41995a2d94d886c5191885c7a779d95d5169bb48a1d63259a00cb7f2f; all 1,296 exported bytes/executable semantics match source. Exported Laravel contract SHA-256 is153a261371272e0fa8e0a6e79dbe425b9adc311cbe596ce0237575a78b0828a7.Validation:
Documentation adoption is live through Docs #545. Protected Pages 43559604709 passed at accepted 4e85eba5; independent producer readback confirms that the public stable selector exactly equals accepted source (SHA-256
fbbe991205d82a231bdd228173cef9c20c20d82933c4235c4773474ec08bea63). The Docs owner records all 48 public pages/eight locales and preserves the separate PHP bridge/other-consumer scope.Final publication and consumer handoff. Workflow #1133 is complete. SDK #422, Sample #345 and affected embedded consumers retain their own source/installed/deployment gates. The merged topic is independently absent; the maintenance branch and immutable tag are retained. No PHP Server or 2.29 release is selected.