Closed rhoerr closed 4 months ago
I stripped out all composer.json changes -- that was a possibly naive assumption on my part that none of those were security related, just updating versions for the patch release. That could use further review as well.
I reviewed composer changes. The primary composer.json shows a change:
- "colinmollenhour/php-redis-session-abstract": "^1.5",
+ "colinmollenhour/php-redis-session-abstract": "~1.5.3",
This is likely to address the breaking change in 1.6.0 of that module.
As far as I can tell, there are no other composer changes of consequence. Only file formatting (probably ran them all through a linter to sort properties), version, internal package constraints.
@Vinai What do we need to be able to move this forward?
I need to cherry pick the commits and resubmit them against 1.x-release
. This PR might still be useful to merge, but for the moment it's irrelevant.
Description (*)
This PR pulls the changes from 2.4.7-p1 vs 2.4.7 onto 2.4-develop (which as of yet does not have them merged in). This is important for security reasons.
I sourced the change list from https://github.com/magento/magento2/compare/2.4.7..2.4.7-p1 with all composer.json changes removed. Summary:
Note that there were a couple merge conflicts, due to changes in 2.4.7-p1 that were already merged or made irrelevant by
2.4-develop
work done since 2.4.7's release. I evaluated the history of each file in question to determine the proper action (which in all cases was to ignore, if I remember correctly). Note particularly that the regex change to/Filesystem/Directory/PathValidator.php
was one of these cases.Questions or comments
Someone please check this PR against the source https://github.com/magento/magento2/compare/2.4.7..2.4.7-p1.patch to verify I did not miss anything.
Contribution checklist (*)