Repository navigation
The YAML parser is the one the advisory is about - #26
Merged
Merged
Conversation
|
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.



The lock holds
symfony/yamlv8.1.9, and an advisory published today covers it:The affected versions are
>=8.1.0,<8.1.11, so v8.1.11 is the one the advisory stopsat, and it is the newest version on the line the lock is on.
The second change in the lock is the directives package's path reference, which moves
from
ffcda3dto1044638— the merge commit of the 0.3.1 release. The lock recordedthe release branch's commit; the pipeline checks out
main, so the lock now says whatthe pipeline installs.
The phpunit advisory is left alone.
phpunit/phpunitv13.4.3 is covered byCVE-2026-119193, which v13.4.4 fixes — but pest v5.3.3 conflicts with phpunit 13.4.4,
so the fix drags a test framework upgrade into a lock file. That advisory is from the
27th of October, it affects the development dependencies only, and it is not what this
change is about.
The site builds, the suite passes (126 tests), and every address on every page still
resolves.