component/php83 is not yet available on bookworm-wikimedia, only bullseye-wikimedia, so we can't test for the OS upgrade in CI consistently.
Update - 2026-02-26
The task title and description have been updated to reflect the currently supported production PHP package component (following the upgrade to 8.3). The component/php83 packages will be rebuilt for bookworm in Q4 FY25-26, following the ICU72 upgrade scheduled for this quarter (Q3).
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T366644 Raise MediaWiki's MariaDB requirement to 10.6 | |||
| Open | None | T366646 Raise Quibble jobs' tested version of MariaDB to 10.6 | |||
| Open | vaughnwalters | T407763 wikilambda-catalyst-end-to-end tests use a more modern browser version than CI, which is stuck on a 2023 vintage browser | |||
| Open | None | T383337 Migrate all CI jobs from Bullseye to Bookworm or later and drop Bullseye testing support | |||
| Open | None | T362705 Migrate Quibble images from bullseye to bookworm | |||
| Open | None | T397075 Package Wikimedia's PHP 8.3 component for bookworm |
@Jdforrester-WMF - This work is not currently planned, no. We won't be upgrading the production images to bookworm (likely as part of a two-step ICU 72 -> bookworm upgrade) until Q3 or Q4, at which point we'll already be on 8.3.
Ah. In that case, we can't start testing MW in CI on bookworm until we've drop PHP 8.1 support from MW the product, which is T358666: Drop PHP 8.1 support from MediaWiki. If the timelines between SRE and MW product don't align, we'll be stuck in an untestable triangle.
Hey @Scott_French, the problem here is that we're committed to testing PHP 8.1 in CI until we drop support for the branches that use it, i.e. 1.43 which is in active support until the end of 2027.
8.3 is nice too, but this was specific to 8.1 for that reason.
@Jdforrester-WMF - Thanks for clarifying. I've reverted the task title and description to reflect that.
As before, for anything that's not specifically tracking the supported {PHP, Debian} version pair used in production, I'd strongly recommend using sury.org packages. Those are what we build from anyway, with only a small handful of additional patches to backport fixes from newer PHP minor versions.
The key issue here is that maintaining parallel components for different pairs is a recipe for confusion, due to the implicit coupling with ICU version (i.e., which we can't afford to get wrong in production, due to the disruption it could cause).
Hmm, yes, you're totally right; I've unwound the CI dependency on WMF's version of PHP 8.1 and re-built CI on Sury 8.1.34, deployed, and tested it; this can now be changed back to what you said, supplying the Wikimedia 8.3 package on bookworm (or trixie, whichever Wikimedia is moving to next, if that's been decided).
Thank you very much for doing so, @Jdforrester-WMF. Great, I'll refocus this on the upcoming work to migrate to 8.3-on-bookworm.