Problem/Motivation

- https://github.com/symfony/symfony/releases/tag/v6.3.0-RC2
- https://github.com/symfony/symfony/releases/tag/v6.3.0

Proposed resolution

Start updating now to Symfony 6.3 to see what deprecations, if any, we need to fix.

Remaining tasks

User interface changes

API changes

Data model changes

Release notes snippet

CommentFileSizeAuthor
#4 3363222-4.patch41.55 KBandypost
#2 3363222-2.patch10.28 KBandypost

Comments

andypost created an issue. See original summary.

andypost’s picture

andypost
he/him
Primary language Russian
commented
Status: Active » Needs review
StatusFileSize
new 3363222-2.patch10.28 KB 
$ ~/.composer/vendor/bin/composer-lock-diff --no-links
+------------------------------+------------+------------+
| Production Changes           | From       | To         |
+------------------------------+------------+------------+
| symfony/console              | v6.3.0-RC1 | v6.3.0-RC2 |
| symfony/dependency-injection | v6.3.0-RC1 | v6.3.0-RC2 |
| symfony/http-kernel          | v6.3.0-RC1 | v6.3.0-RC2 |
| symfony/validator            | v6.3.0-RC1 | v6.3.0-RC2 |
| symfony/var-dumper           | v6.3.0-RC1 | v6.3.0-RC2 |
+------------------------------+------------+------------+
spokje’s picture

spokje
Primary language Dutch
commented
Status: Needs review » Reviewed & tested by the community
andypost’s picture

andypost
he/him
Primary language Russian
commented
Title: Update to Symfony 6.3 RC2 » Update to Symfony 6.3
Issue summary: View changes
Status: Reviewed & tested by the community » Needs review
StatusFileSize
new 3363222-4.patch41.55 KB

https://github.com/symfony/symfony/releases/tag/v6.3.0

smustgrave’s picture

smustgrave commented
Status: Needs review » Reviewed & tested by the community

All green

  • catch committed fc54b618 on 10.1.x 
    Issue #3363222 by andypost: Update to Symfony 6.3

  • catch committed 96115eaa on 11.x 
    Issue #3363222 by andypost: Update to Symfony 6.3
catch’s picture

catch
he/him
Primary language English
commented
Status: Reviewed & tested by the community » Fixed

Committed/pushed to 11.x and 10.1.x, thanks!

cilefen’s picture

cilefen commented

#3364801: PHP Fatal error: Declaration of Drupal\Core\TypedData\Validation\ExecutionContext

ankitv18’s picture

ankitv18 commented

Are these changes also gonna pushed into Drupal 10.0.x branch?

catch’s picture

catch
he/him
Primary language English
commented

@ankitv18 no that will stay on Symfony 6.2, and then 10.0.x goes out of support the end of this year.

lmoeni’s picture

lmoeni
she/her
commented

The current requirement in 10.0.x for example allows symfony/console 6.3 to install. Which then results in this issue:
https://www.drupal.org/project/drupal/issues/3364801
Shouldn't we backport or lock the version to 6.2 then?

cilefen’s picture

cilefen commented

Does that occur with the core-recommend package at 10.0.*?

chi’s picture

chi commented
Status: Fixed » Needs work

Shouldn't we backport or lock the version to 6.2 then?

Yes, we should. core-recommended package should not be used to obscure wrong dependency ranges.
Not sure which way is better. Drupal 10.0 is not compatible with Symfony 6.3 and Drupal 10.1.0 is not released yet. So right now we have no stable Drupal release compatible with Symfony 6.3.

chi’s picture

chi commented

no that will stay on Symfony 6.2, and then 10.0.x goes out of support the end of this year

And Symfony 6.2 will go out of suport next month which means for Drupal 10.0 will use unsupported Symfony version for a few month.

catch’s picture

catch
he/him
Primary language English
commented

@Chi we have an arrangement with the Symfony project that two Drupal core committers are on their security team. If any components in a Symfony minor release that Drupal core still depends on have a security advisory issued, then we will work with them to get the fix backported to the branch we're using and they'll issue a 'bonus' release for it. This doesn't apply to components we don't use.

It is a bit obscure, but it is what we settled on - they didn't want to support their own minor releases for 13 months, we didn't want to update to their minor releases in our patch releases, we didn't want to be out of security support for six months on a permanent basis.

chi’s picture

chi commented

Re #16. Makes sense.
We still need to lock Drupal 10.0 on Symfony 6.2 in composer.json.

spokje’s picture

spokje
Primary language Dutch
commented
Related issues: +#3365567: Lock Drupal 10.0 on symfony/serializer and symfony/validator 6.2

We still need to lock Drupal 10.0 on Symfony 6.2 in composer.json.

#3365567: Lock Drupal 10.0 on symfony/serializer and symfony/validator 6.2, putting this one back to status Fixed, since there's nothing more to do here.

chi’s picture

chi commented
Status: Needs work » Fixed

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.