Skip to content

Update active Symfony fixture locks for security fixes - #1032

Merged
rmcdaniel merged 1 commit into
mainfrom
deps/970-symfony-security-20261104
Nov 4, 2026
Merged

rmcdaniel merged 1 commit into
mainfrom
deps/970-symfony-security-20261104

Conversation

@rmcdaniel

Copy link
Copy Markdown
Member

The three active Composer fixtures now select the fixed Symfony patches for the November 4 advisories. Current queue and embedded HTTP use 7.4.23; embedded replay uses 8.1.11. This removes the newly reported HTTP Foundation, HTTP Kernel, Routing, Yaml and applicable HttpClient findings from their locked graphs.

Exactly four package records change in current queue, four in replay and five in embedded HTTP. All unrelated package objects, top-level lock metadata, manifests and published Workflow references are unchanged. The two historical #773/#809 lock inputs remain reserved and unchanged. The recurring inventory/audit guard is a separate #970 continuation.

Validation: all three exact final locks pass Composer 2.10.3 strict validation and fresh complete audit with no advisories, ignored/filtered findings or abandoned packages. Every dependency request used the reviewed central verifier and authenticated 120-certificate CA bundle. No package was installed in this metadata phase; fixture installation/smokes and independent Security review are pending. One initial embedded-HTTP solve refused the minimal image's missing sockets extension; the existing PHP 8.4.27 toolchain supplied it without a platform bypass. Normal hosted checks are requested by this draft.

Refs #970. This source change does not publish a package, execute the historical studies or modify any release/operational gate.

@sonarqubecloud

sonarqubecloud Bot commented Nov 4, 2026

Copy link
Copy Markdown

@rmcdaniel

Copy link
Copy Markdown
Member Author

Security source checkpoint for exact head 6f3fc63287b4a3f8fe8d355969c785ea2991d93f, base 431aba231c05b5cde14c2228deb115ac1ef7b438, tree 89697d31b9710f3771e3fd4a1b95786b33ff9bbe: source scope is correct; final PASS remains held for terminal exact-head checks and the declared installed fixture smokes.

Independent canonical lock comparison confirms:

  • .github/queue-contention/current/composer.lock: exactly HttpFoundation, HttpKernel, Routing, and Yaml change to 7.4.23;
  • benchmarks/embedded-replay/composer.lock: exactly the same four packages change to 8.1.11;
  • examples/embedded-http/composer.lock: exactly those four plus HttpClient change to 7.4.23;
  • no packages-dev object and no top-level lock field changes in any lock;
  • both historical queue/tracing locks and every other file are absent from the diff.

The split-package tag targets independently resolve to the exact lock references: HttpClient ed012bfca0f7b45d97016efcdf9b0639c52a1722; HttpFoundation 7fb73cffa06e2bcc2cb523fcccb1e8174106b206 / 30fa3efe6e736b0d06f5331cc6abe813582c0a26; HttpKernel 94c57f4c5c45a311d244a0aeadb72b14ee41d25d / 460658504e26a2794aa614b4fbe6cf9bac2076fe; Routing 0000ade604b7bc798cb1e75edf6f17df48185f73 / f3fefc6cad3748d538be970ca81b71f06d7aa8b3; Yaml 1e601207ffe627a2e621faa9d661f1d32dcf1cec / e8266f55160f674f290a5f567cb55e11e21f921b.

These are the upstream fixed same-minor floors for the November 4 batch. No audit exception is added. Keep #773/#809 and their execution stops separate; this checkpoint does not accept those historical locks or the recurring-guard WIP.

Required before final carry: all authoritative check records terminal on this head, fresh locked-audit/strict-validation receipts retained, and the three actual installed fixture smokes bind these exact lock bytes without overlays or source mutation. General retains merge; no product deployment/release clearance is implied.

@rmcdaniel

Copy link
Copy Markdown
Member Author

Fresh representative installed-fixture qualification is complete for exact #1032 head 6f3fc63287b4a3f8fe8d355969c785ea2991d93f, tree 89697d31b9710f3771e3fd4a1b95786b33ff9bbe, base 431aba231c05b5cde14c2228deb115ac1ef7b438.

All three consumers were installed normally from their exact committed locks using PHP 8.4.27 / Composer 2.10.3, scripts/plugins disabled, with authenticated central trust verified before each dependency request. Installed platform requirements pass. No library source overlay was used.

  • Embedded replay: the original pinned PHP 8.5.6 image, one round/repetition and original 1 CPU/1 GiB/no-swap envelope pass 1 test / 40 assertions, 14 events, seven tasks and three activity effects.
  • Embedded HTTP: the actual Laravel 12.69.3 HTTP kernel refuses an unauthenticated request (401), admits an authenticated workflow (202), executes the real SQLite database queue, and returns a completed read (200) with the exact int64/null/Unicode activity result. No jobs or failed jobs remain. This is an in-process functional check with no Octane/network/performance claim.
  • Current queue fixture: the unchanged limited-cohort command under its original 2 CPU/2 GiB/no-swap cap and 90-second deadline completes 64 activities / 64 attempts / 66 tasks, one effect per original, zero repairs/jobs/failed jobs, exact output and preserved original history/timing.

All 937 / 934 / 939 installed Core source/resource files match their immutable published references before and after, and all 2,326 candidate source inputs remain exact. An initial HTTP setup stopped because the example-required /state storage was not mounted; only the disposable mount/setup was corrected, with its failure retained. The corrected remaining checks finish inside the original owner ceiling. All task containers are independently absent; owned source/vendor/database/state scratch is removed after copying bounded review evidence. No historical experiment, Server, image build or production action ran.

Fresh exact-head hosted rollup is also terminal with no failing or pending check. The narrow source/graph proof and all three current installed smokes are returned for final independent Security carry; normal source merge remains General-owned. The separate recurring guard/historical exception/trust work on #970 remains open, and no package/release/operational clearance follows.

@rmcdaniel

Copy link
Copy Markdown
Member Author

Security final PASS — exact source, hosted, and installed-fixture carry

Security's exact-source checkpoint is retained unchanged for head 6f3fc63287b4a3f8fe8d355969c785ea2991d93f, base 431aba231c05b5cde14c2228deb115ac1ef7b438, tree 89697d31b9710f3771e3fd4a1b95786b33ff9bbe. The PR remains draft, mergeable/CLEAN, with exactly the three reviewed active fixture locks changed and no source drift.

The two held gates are now satisfied:

  • authoritative exact-head provider readback has all 24 checks terminal: 17 success and seven intended matrix/coverage skips, with no failure or nonterminal record. CodeQL is successful and the open PR-ref alert set is empty;
  • the fresh installed-fixture packet binds the same tuple and exercises all three exact committed locks under authenticated central trust with scripts/plugins disabled and no source overlay. Embedded replay passes 1 test / 40 assertions; the real Laravel HTTP kernel performs the expected 401/202/200 auth-to-database-queue-to-typed-result path with no residual jobs; and the current limited cohort completes 64 activities / 64 attempts / 66 tasks with zero repairs/jobs/failures.

The installed packet also verifies 937 / 934 / 939 Core source/resource files against their immutable published references before and after, all 2,326 candidate source inputs unchanged, and final task-container/scratch absence. The disclosed initial missing /state disposable-mount setup failure occurred before workflow admission and is not counted as acceptance evidence; its bounded correction did not change source or extend the original owner ceiling.

Disposition: PASS for General's normal source merge decision on this exact head/base/tree. This accepts the narrow active-fixture advisory repair only. It does not waive or close the separate recurring audit/trust and historical-lock work on #970, authorize a package/release/deployment/runtime action, or transfer clearance to a later source/head.

@rmcdaniel
rmcdaniel marked this pull request as ready for review November 4, 2026 20:30
@rmcdaniel
rmcdaniel merged commit b3dd00e into main Nov 4, 2026
24 checks passed
@rmcdaniel

Copy link
Copy Markdown
Member Author

General exact-head source integration is complete.

Normal merge b3dd00e96440c4bcc70a3853f662bf93311e7029 has ordered parents 431aba231c05b5cde14c2228deb115ac1ef7b438 and 6f3fc63287b4a3f8fe8d355969c785ea2991d93f, with tree 89697d31b9710f3771e3fd4a1b95786b33ff9bbe exactly equal to the Security-reviewed candidate. Fresh head/base, main, terminal checks and Security disposition #1032 (comment) were reconciled before the normal merge. Main and merged PR readback agree.

This accepts source integration only. Ordinary main checks and the owner's acceptance readback remain required. Every package, tag, release, published-runtime, installed-artifact and downstream gate remains separate; no such action follows from this merge.

@rmcdaniel

Copy link
Copy Markdown
Member Author

General independently accepts ordinary main b3dd00e96440c4bcc70a3853f662bf93311e7029 after the normal source merge: ordered parents remain 431aba231c05b5cde14c2228deb115ac1ef7b438 and 6f3fc63287b4a3f8fe8d355969c785ea2991d93f, tree 89697d31b9710f3771e3fd4a1b95786b33ff9bbe equals the Security-reviewed candidate. Fresh provider readback has all28 check records terminal,26success/two intended skips, with no failure or pending. All four original exact-main workflows are completed/success at attempt1; direct job reads show the build's22success/two intended skips plus four successful boundary/target/quality jobs. No log-only or aggregate-only acceptance is used.

The three actual installed fixture proofs and exact Core-source equalities remain in6641306985; Security6641360728 is unchanged. Source integration and ordinary main are accepted. #970 stays open for the maintained full-lock inventory, trust migration, historical classification and recurring audit. Existing historical locks, benchmark interpretation, producer/runtime/release and operator stops remain unchanged. Merged branch cleanup will preserve the earlier combined942a95b reference and any live dependent work.

@rmcdaniel
rmcdaniel deleted the deps/970-symfony-security-20261104 branch November 4, 2026 21:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant