CI: disable Composer audit.block-insecure to ride out advisory waves#76
Merged
Conversation
Three new symfony/yaml advisories landed on Packagist on 2026-05-20 (CVE-2026-45304, CVE-2026-45305, CVE-2026-45133), all flagging the exact symfony/yaml version pinned by every MediaWiki branch in the matrix (5.4.23 on REL1_39 through 5.4.45 on REL1_43, etc.). Composer's `audit.block-insecure` default refuses to load the flagged version, so `composer update` (and `composer install` inside installWiki.sh) fails for every PR. Disable `audit.block-insecure` globally before any composer step. Mirrors the upstream MediaWiki backport (Phabricator T416518, commit ef90ede), which set the same flag in mediawiki/core's composer.json on REL1_43+ and master — applied at the CI level here so it also covers EOL branches (REL1_39-REL1_42) that didn't receive the backport, and the installWiki.sh `composer install` path on cache miss (via shared ~/.composer/config.json). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
malberts
force-pushed
the
ci/disable-composer-block-insecure
branch
from
29dd7a4 to
b7c5fb1
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
Three new
symfony/yamladvisories landed on Packagist on 2026-05-20:PKSA-v5yj-8nmz-sk2q— CVE-2026-45304 ("Billion Laughs" exponential memory)PKSA-ft77-7h5f-p3r6— CVE-2026-45305 (ReDoS inParser::cleanup())PKSA-b14r-zh1d-vdrc— CVE-2026-45133 (stack exhaustion via unbounded recursion)They flag the exact
symfony/yamlversions pinned by every MediaWiki branch in the CI matrix — 5.4.23 on REL1_39, 5.4.45 on REL1_43, etc. Composer'saudit.block-insecuredefault refuses to load any flagged package, socomposer update(andcomposer installinsideinstallWiki.shon cache miss) now fails for every PR with:Visible casualty: #75. Master will trip on it the next time CI runs too.
Cache-busting won't help here — REL1_39–REL1_42 are EOL and don't have the upstream
"audit": {"block-insecure": false}backport that REL1_43+/master got via Phabricator T416518 / commit ef90ede. Refetching them gets the same vulnerable pin back.What
Add one step right after
Setup PHP:composer config --global audit.block-insecure false. It writes to~/.composer/config.json, so every subsequent composer invocation in the same job — bothcomposer installinsideinstallWiki.sh(cache-miss path) and the workflow's owncomposer update(cache-hit path) — inherits the flag and ignores the advisory block.It mirrors at the CI layer what the upstream MediaWiki backport (T416518) already does inside
mediawiki/core/composer.jsonon REL1_43+ / master.Three lines of YAML, no other changes. Once this merges, #75 (and any other open PR) should go green on rebase / rerun without further changes.
🤖 Generated with Claude Code