Repository navigation
ci: ignore the blocked symfony/yaml and guzzle versions in composer update - #1959
Merged
mrrobot47 merged 1 commit intoNov 4, 2026
Merged
Conversation
…pdate Composer 2.11 refuses symfony/yaml 4.4, guzzlehttp/psr7 1.x and guzzlehttp/guzzle 7.8 because of security advisories, so every develop and PR build fails at "Install dependencies". Ignore exactly these packages at these versions, only for the composer update path in CI, until they are upgraded. The committed composer.json and lock, and the master/tag builds from the lock, are unchanged.
Contributor
There was a problem hiding this comment.
🟡 Changes recommended
The test-job condition incorrectly applies advisory exceptions to release tags, which should retain the existing lock-file-based composer install behavior.
1 open issue
What changed in this PR
Adds a temporary CI-only workaround for Composer advisory blocks so dependency updates can proceed while dependency upgrades are planned.
Changes:
- Defines version-scoped advisory exceptions for
symfony/yaml,guzzlehttp/psr7, andguzzlehttp/guzzle, while keeping audit reporting enabled. - Applies the exceptions before
composer updatein the build and test jobs without changing committed Composer files.
| File | Description |
|---|---|
.github/workflows/test_and_build.yml |
Defines shared advisory exceptions and applies them to dependency-update steps. |
Review effort: Balanced
This was referenced Nov 4, 2026
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
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.

Since 2026-11-01, Composer 2.11 on the runners refuses symfony/yaml 4.4.* (CVE-2026-109413, CVE-2026-45304, CVE-2026-45305, CVE-2026-45133), guzzlehttp/psr7 1.x (CVE-2026-59882 and five more) and, behind it, guzzlehttp/guzzle 7.8 (the last guzzle 7 line that accepts psr7 1.x), so every develop push and PR build fails at "Install dependencies" and no tests run.
This is a CI-only stopgap. On the
composer updatepath (develop and PRs), the workflow addsconfig.policy.advisories.ignoreentries for exactly these three packages, each limited to the version line in use (symfony/yaml4.4.,guzzlehttp/psr71.9.,guzzlehttp/guzzle7.8.*), withon-audit: falsesocomposer auditstill reports them. Nothing else is unblocked: any other package with an advisory, or a newer advisory-affected version of these, still fails the build.Not changed: the committed
composer.jsonandcomposer.lock, and the phar build for master and tags, which runscomposer installfrom the lock and isn't blocked. The Behat job only takes the lock path on master (as before); on tags it already rancomposer update, so it gets the ignore too, which keeps the next release tag's tests from failing the same way.The real fix, moving to a fixed symfony/yaml (with the Symfony 4.4 components and Behat that come with it) and to acmephp/core 2.x with guzzlehttp/psr7 2.x and a current guzzle, is planned for v4.15.0. The ignore goes away with it.