Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.Follow-up to #2386585: Upgrade to Symfony 2.6.1 and #2377281: Upgrade to Symfony 2.6 stable.
Symfony 2.6.4 is out. I think we should upgrade since we are tracking stables. This is critical as this is an external library upgrade. Please downgrade if minor version upgrades are not really critical. This should be a quickfix, so I don't think there would be a problem.
Note: From the changelog, it seems there are security related fixes/improvements which may or may not be applicable to us. But it is still a good idea to update.
Beta phase evaluation
| Issue category | Task because it is an external library upgrade. |
|---|---|
| Issue priority | Critical because this is an external library upgrade. |
| Disruption | Not disruptive. |
| Comment | File | Size | Author |
|---|---|---|---|
| #11 | interdiff.txt | 1.51 KB | dawehner |
| #11 | 2414235-11.patch | 636.37 KB | dawehner |
| #4 | upgrade_to_symfony_2_6_3-2414235-4.patch | 734.27 KB | hussainweb |
Comments
Comment #1
hussainwebAttaching updates after running composer update symfony/*. There is no need to change composer.json here.
Comment #2
catchPer #2400407: [meta] Ensure vendor (PHP) libraries are on latest stable release minor releases are critical.
However this is a patch-level release so shouldn't be. The reasons to not have patch-level releases as critical are that they may not have relevant changes for us, or only normal/minor bug fixes,a nd also it should be straightforward to skip a patch-level release and go to the next one once it's out.
So downgrading to major. If there's something in this release that should independently be a release blocker, we should upgrade it again.
And of course it's still good to keep up to date even if the issue isn't critical.
Comment #3
hussainwebAgreed on this. I think we can still go ahead with this update on priority to keep the subsequent upgrades even smaller. And it will be good to stay on top of those minor/normal bugs as well. :)
I know this is essentially what you are saying but I am just making a point that keeping it critical can sometimes move a quickfix release like this very quickly. I have no problems with this being major as well. This was just a running thought.
Lastly, I am just marking an issue that does depend on this (not blocked, just affected).
Comment #4
hussainwebSymfony 2.6.4 is out.
Comment #6
hussainwebA minor upgrade shouldn't break anything. This doesn't look like an usual random failure but there is a chance. It could also be a sign of broken HEAD, but I don't see the same failures in other patches around this time.
I think we should retest this just once to make sure.
Comment #9
hussainwebIt looks like a valid test failure. If this is a breakage/regression, this should be a critical issue to resolve immediately rather than waiting for next major release.
I can't debug through this today, but will try tonight or tomorrow. Feel free to downgrade this if it doesn't look like a critical issue.
Comment #10
dawehnerWow, I'll try to see which commit in symfony caused that
Comment #11
dawehnerIt seems to be for me that we have a wrong setup for this 2 tests.
If you request a site on the frontpage using a subdir installation the path is indeed "/subdir/" but our tests assumed "/subdir".
https://github.com/symfony/symfony/pull/13039 was the corresponding symfony issue.
Comment #12
catchNIce work tracking the upgrades and the fix.
This also contains https://github.com/symfony/symfony/pull/13262 which helps with #1920902: Add a Drupal Yaml wrapper so we can default to PECL Yaml component if it is available.
RTBC for me.
Comment #13
alexpottCommitted 1003720 and pushed to 8.0.x. Thanks!
Thanks for adding the beta evaluation to the issue summary.