Symfony update 5.4.43 (from recent update to 5.4.42 but now .43 is out) #31034
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.
Overview
We just updated to 5.4.42 but 3 days ago symfony put out 5.4.43 - seems silly to upgrade but not to the one that is the latest when we tag
Before
just updated to 5.4.42
After
composer update -W symfony/*
Gathering patches for root package.
Loading composer repositories with package information Updating dependencies
Lock file operations: 0 installs, 3 updates, 0 removals
Technical Details
The key PR is
symfony/symfony#57493
And I note that it seems like a sleeper bug depending on server config- ie
symfony/symfony#57493 (comment) "Ubuntu will join impacted systems on October 10 when 24.10 is released." The final summary says there are no deprecations but this comment
symfony/symfony#57493 (comment) suggests there might be
I don't really know if we have security bundles but it seems like this fixes a bug that occurs when libxml libraries are used but it adds a deprecation. Also our composer-installing instances will be getting this fix so it will be less confusing to patch the tarball
Comments