Skip to content

ci(behat): ignore the symfony/config and symfony/serializer advisories - #123

Merged
mrrobot47 merged 2 commits into
EasyEngine:developfrom
mrrobot47:ci/advisory-ignore-symfony-config-serializer
Nov 16, 2026
Merged

mrrobot47 merged 2 commits into
EasyEngine:developfrom
mrrobot47:ci/advisory-ignore-symfony-config-serializer

Conversation

@mrrobot47

@mrrobot47 mrrobot47 commented Nov 15, 2026 •

Copy link
Copy Markdown
Member

Since 2026-11-04, Packagist flags symfony/config 4.4.* (PKSA-9myg-zzdn-22rg; required by core's root composer.json and by behat/behat 3.8.1) and symfony/serializer 3.4.20 (PKSA-nyd8-k74r-fsf2, PKSA-grh8-hvfp-h9pf; pinned by site-command). This workflow's last develop run was green on 2026-11-04, before these were published, but it clones core develop and resolves site-command dev-develop, so the next run fails at "Set up EasyEngine core" (composer update) the same way as site-command's develop run https://github.com/EasyEngine/site-command/actions/runs/43711582837 (21/21 jobs).

This adds both packages to the existing ADVISORY_IGNORE in behat.yml, with on-audit: false, the same way as the symfony/yaml and guzzle entries. Note that Composer uses an entry's constraint only for audit output: when resolving, a package entry unblocks every version of that package, so a follow-up will switch all the entries to policy.advisories.ignore-id with the advisory IDs.

CI-only. The committed composer.json is unchanged, and this workflow only tests; the phar it builds stays on the runner, and the shipped phar is built in core.

The PR also pins the Behat jobs to runs-on: ubuntu-24.04. ubuntu-latest now resolves to ubuntu-26.04, whose sudo-rs ignores sudo -E ("preserving the entire environment is not supported"), so the Pebble settings no longer reach Behat and the le lane's Let's Encrypt scenarios are refused even with the dependencies installed. 24.04 is the image these suites last passed on; the pin can go once the workflow passes those variables explicitly (for example sudo --preserve-env=...).

The real fix, the Symfony and Behat upgrade, is tracked separately; the ignore goes away with it.

Packagist now flags symfony/config 4.4 (PKSA-9myg-zzdn-22rg) and symfony/serializer 3.4.20 (PKSA-nyd8-k74r-fsf2, PKSA-grh8-hvfp-h9pf), so composer update of the cloned core fails before Behat starts. Ignore exactly these versions in CI, like the existing entries, until the Symfony and Behat upgrade. The committed composer.json and lock are unchanged.
ubuntu-latest now resolves to ubuntu-26.04, whose sudo-rs ignores `sudo -E`, so the variables the suite needs (EE_BEHAT_* guards, RCLONE_CONFIG, the Pebble settings) no longer reach Behat under sudo and the guarded, backup and Let's Encrypt scenarios fail. Pin the image the suites last passed on until the workflow passes those variables explicitly.
@mrrobot47
mrrobot47 merged commit f7772c0 into EasyEngine:develop Nov 16, 2026
22 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant