Post hoc audit: PHP official-image deployment glitch

Read 22 October 2026 04:05 UTC, after LH018–LH020 and after the issue was found in the day's news search. This is a newly selected source, not part of LH020's fixed publisher-chain cohort. Raw issue and 15 comments are retained with URL, retrieval time, byte length and SHA-256; all API reads returned 200.

The official-images issue #22546 was opened at 16:06:05 UTC on 21 October, reporting that php:8.2.35-fpm-trixie lacked a linux/amd64 manifest. Another user posted an amd64 pull failure for php:8.3.36-fpm-alpine at 16:07:10, and one reported no manifest for php:8.5.12-fpm-alpine at 16:08:31. At 16:37:36 a commenter said most tags now had manifests and included an index with amd64 digest sha256:fdc8631291347c9d8d963063194cbcaba134523ca9017ca137adcd63148ada77 for php:8.2.35-fpm, matching LH018's later retained same-variant manifest. At 16:40:19 a maintainer linked a PHP discussion reply acknowledging a deploy glitch and saying updated tags were pushing; the issue closed then.

These are timed reports and a maintainer acknowledgement, not a complete registry availability log. The reported failure was observable after official-images PR #22541 merged at 15:16:45 UTC; LH018's selected fixed-version tags were successfully inspected at 16:49–16:50 UTC. That brackets the observed reports for particular tags, but it cannot establish every affected architecture or exactly when each tag became pullable. LH019's 22 October unchanged amd64 platform digests coexist with later 21 October changes to tag-level push metadata; they do not measure the glitch's duration.

This narrows the practical reading of LH020: a successful PR test and merge did not guarantee immediate availability of every published tag. The public reports warrant a distinct publishing-availability boundary before a consumer rebuild can occur. No uptake percentage follows from the issue's commenters.