symfony · priyadi · Nov 22, 2023 · Nov 22, 2023 · Nov 23, 2023 · Nov 23, 2023
diff --git a/.doctor-rst.yaml b/.doctor-rst.yaml
@@ -69,16 +69,16 @@ rules:
 
     #   master
     versionadded_directive_major_version:
-        major_version: 6
+        major_version: 7
 
     versionadded_directive_min_version:
-        min_version: '6.0'
+        min_version: '7.0'
 
     deprecated_directive_major_version:
-        major_version: 6
+        major_version: 7
 
     deprecated_directive_min_version:
-        min_version: '6.0'
+        min_version: '7.0'
 
 exclude_rule_for_file:
     - path: configuration/multiple_kernels.rst

diff --git a/_build/redirection_map b/_build/redirection_map
@@ -526,6 +526,7 @@
 /components https://symfony.com/components
 /components/index https://symfony.com/components
 /serializer/normalizers /components/serializer#normalizers
+/components/serializer#component-serializer-attributes-groups-annotations /components/serializer#component-serializer-attributes-groups-attributes
 /logging/monolog_regex_based_excludes /logging/monolog_exclude_http_codes
 /security/named_encoders /security/named_hashers
 /components/inflector /components/string#inflector

diff --git a/_includes/_annotation_loader_tip.rst.inc b/_includes/_annotation_loader_tip.rst.inc
diff --git a/bundles.rst b/bundles.rst
@@ -55,11 +55,6 @@ Start by creating a new class called ``AcmeTestBundle``::
     {
     }
 
-.. versionadded:: 6.1
-
-    The :class:`Symfony\\Component\\HttpKernel\\Bundle\\AbstractBundle` was
-    introduced in Symfony 6.1.
-
 .. caution::
 
     If your bundle must be compatible with previous Symfony versions you have to

diff --git a/bundles/configuration.rst b/bundles/configuration.rst
@@ -320,10 +320,6 @@ In your extension, you can load this and dynamically set its arguments::
 Using the AbstractBundle Class
 ------------------------------
 
-.. versionadded:: 6.1
-
-    The ``AbstractBundle`` class was introduced in Symfony 6.1.
-
 As an alternative, instead of creating an extension and configuration class as
 shown in the previous section, you can also extend
 :class:`Symfony\\Component\\HttpKernel\\Bundle\\AbstractBundle` to add this

diff --git a/bundles/extension.rst b/bundles/extension.rst
@@ -111,10 +111,6 @@ To read more about it, see the ":doc:`/bundles/configuration`" article.
 Loading Services directly in your Bundle class
 ----------------------------------------------
 
-.. versionadded:: 6.1
-
-    The ``AbstractBundle`` class was introduced in Symfony 6.1.
-
 Alternatively, you can define and load services configuration directly in a
 bundle class instead of creating a specific ``Extension`` class. You can do
 this by extending from :class:`Symfony\\Component\\HttpKernel\\Bundle\\AbstractBundle`

diff --git a/bundles/prepend_extension.rst b/bundles/prepend_extension.rst
@@ -154,10 +154,6 @@ registered and the ``entity_manager_name`` setting for ``acme_hello`` is set to
 Prepending Extension in the Bundle Class
 ----------------------------------------
 
-.. versionadded:: 6.1
-
-    The ``AbstractBundle`` class was introduced in Symfony 6.1.
-
 You can also append or prepend extension configuration directly in your
 Bundle class if you extend from the :class:`Symfony\\Component\\HttpKernel\\Bundle\\AbstractBundle`
 class and define the :method:`Symfony\\Component\\HttpKernel\\Bundle\\AbstractBundle::prependExtension`
@@ -190,6 +186,34 @@ method::
 
     The ``prependExtension()`` method, like ``prepend()``, is called only at compile time.
 
+Alternatively, you can use the ``prepend`` parameter of the
+:method:`Symfony\\Component\\DependencyInjection\\Loader\\ContainerConfigurator::extension`
+method::
+
+    use Symfony\Component\DependencyInjection\ContainerBuilder;
+    use Symfony\Component\DependencyInjection\Loader\Configurator\ContainerConfigurator;
+    use Symfony\Component\HttpKernel\Bundle\AbstractBundle;
+
+    class FooBundle extends AbstractBundle
+    {
+        public function prependExtension(ContainerConfigurator $containerConfigurator, ContainerBuilder $containerBuilder): void
+        {
+            // ...
+
+            $containerConfigurator->extension('framework', [
+                'cache' => ['prefix_seed' => 'foo/bar'],
+            ], prepend: true);
+
+            // ...
+        }
+    }
+
+.. versionadded:: 7.1
+
+    The ``prepend`` parameter of the
+    :method:`Symfony\\Component\\DependencyInjection\\Loader\\ContainerConfigurator::extension`
+    method was added in Symfony 7.1.
+
 More than one Bundle using PrependExtensionInterface
 ----------------------------------------------------
 

diff --git a/cache.rst b/cache.rst
@@ -745,20 +745,12 @@ Clear all cache pools:
 
     $ php bin/console cache:pool:clear --all
 
-.. versionadded:: 6.3
-
-    The ``--all`` option was introduced in Symfony 6.3.
-
 Clear all cache pools except some:
 
 .. code-block:: terminal
 
     $ php bin/console cache:pool:clear --all --exclude=my_cache_pool --exclude=another_cache_pool
 
-.. versionadded:: 6.4
-
-    The ``--exclude`` option was introduced in Symfony 6.4.
-
 Clear all caches everywhere:
 
 .. code-block:: terminal
@@ -767,10 +759,6 @@ Clear all caches everywhere:
 
 Clear cache by tag(s):
 
-.. versionadded:: 6.1
-
-    The ``cache:pool:invalidate-tags`` command was introduced in Symfony 6.1.
-
 .. code-block:: terminal
 
     # invalidate tag1 from all taggable pools

diff --git a/components/browser_kit.rst b/components/browser_kit.rst
@@ -130,10 +130,6 @@ on a link::
     // ... and `clickLink()`
     $crawler = $client->clickLink('Go elsewhere...', ['X-Custom-Header' => 'Some data']);
 
-.. versionadded:: 6.4
-
-    The ``serverParameters`` parameter was introduced in Symfony 6.4.
-
 Submitting Forms
 ~~~~~~~~~~~~~~~~
 
@@ -403,10 +399,6 @@ to call ``json_decode()`` explicitly::
     $response = $browser->getResponse()->toArray();
     // $response is a PHP array of the decoded JSON contents
 
-.. versionadded:: 6.1
-
-    The ``toArray()`` method was introduced in Symfony 6.1.
-
 Learn more
 ----------
 

diff --git a/components/cache/adapters/couchbasebucket_adapter.rst b/components/cache/adapters/couchbasebucket_adapter.rst
@@ -1,6 +1,12 @@
 Couchbase Bucket Cache Adapter
 ==============================
 
+.. deprecated:: 7.1
+
+    The ``CouchbaseBucketAdapter`` is deprecated since Symfony 7.1, use the
+    :doc:`CouchbaseCollectionAdapter </components/cache/adapters/couchbasecollection_adapter>`
+    instead.
+
 This adapter stores the values in-memory using one (or more) `Couchbase server`_
 instances. Unlike the :doc:`APCu adapter </components/cache/adapters/apcu_adapter>`, and similarly to the
 :doc:`Memcached adapter </components/cache/adapters/memcached_adapter>`, it is not limited to the current server's

diff --git a/components/cache/adapters/doctrine_dbal_adapter.rst b/components/cache/adapters/doctrine_dbal_adapter.rst
@@ -39,5 +39,22 @@ optional arguments::
     necessary to detect the database engine and version without opening the
     connection.
 
+The adapter uses SQL syntax that is optimized for database server that it is connected to.
+The following database servers are known to be compatible:
+
+* MySQL 5.7 and newer
+* MariaDB 10.2 and newer
+* Oracle 10g and newer
+* SQL Server 2012 and newer
+* SQLite 3.24 or later
+* PostgreSQL 9.5 or later
+
+.. note::
+
+    Newer releases of Doctrine DBAL might increase these minimal versions. Check
+    the manual page on `Doctrine DBAL Platforms`_ if your database server is
+    compatible with the installed Doctrine DBAL version.
+
 .. _`Doctrine DBAL Connection`: https://github.com/doctrine/dbal/blob/master/src/Connection.php
-.. _`Doctrine DBAL URL`: https://www.doctrine-project.org/projects/doctrine-dbal/en/latest/reference/configuration.html#connecting-using-a-url
+.. _`Doctrine DBAL URL`: https://www.doctrine-project.org/projects/doctrine-dbal/en/current/reference/configuration.html#connecting-using-a-url
+.. _`Doctrine DBAL Platforms`: https://www.doctrine-project.org/projects/doctrine-dbal/en/current/reference/platforms.html
diff --git a/components/cache/adapters/redis_adapter.rst b/components/cache/adapters/redis_adapter.rst
@@ -41,10 +41,6 @@ as the second and third parameters::
         $defaultLifetime = 0
     );
 
-.. versionadded:: 6.3
-
-    Support for `Relay`_ was introduced in Symfony 6.3.
-
 Configure the Connection
 ------------------------
 
@@ -163,10 +159,6 @@ array of ``key => value`` pairs representing option names and their respective v
 Available Options
 ~~~~~~~~~~~~~~~~~
 
-.. versionadded:: 6.3
-
-    ``\Relay\Relay`` support was introduced in Symfony 6.3.
-
 ``class`` (type: ``string``, default: ``null``)
     Specifies the connection library to return, either ``\Redis``, ``\Relay\Relay`` or ``\Predis\Client``.
     If none is specified, fallback value is in following order, depending which one is available first:
@@ -208,6 +200,9 @@ Available Options
 ``redis_sentinel`` (type: ``string``, default: ``null``)
     Specifies the master name connected to the sentinels.
 
+``sentinel_master`` (type: ``string``, default: ``null``)
+    Alias of ``redis_sentinel`` option.
+
 ``dbindex`` (type: ``int``, default: ``0``)
     Specifies the database index to select.
 
@@ -219,6 +214,11 @@ Available Options
 ``ssl`` (type: ``array``, default: ``null``)
     SSL context options. See `php.net/context.ssl`_ for more information.
 
+.. versionadded:: 7.1
+
+    The option `sentinel_master` as an alias for `redis_sentinel` was introduced
+    in Symfony 7.1.
+
 .. note::
 
     When using the `Predis`_ library some additional Predis-specific options are available.

diff --git a/components/clock.rst b/components/clock.rst
@@ -1,10 +1,6 @@
 The Clock Component
 ===================
 
-.. versionadded:: 6.2
-
-    The Clock component was introduced in Symfony 6.2
-
 The Clock component decouples applications from the system clock. This allows
 you to fix time to improve testability of time-sensitive logic.
 
@@ -79,16 +75,6 @@ When using the Clock component, you manipulate
 :class:`Symfony\\Component\\Clock\\DatePoint` instances. You can learn more
 about it in :ref:`the dedicated section <clock_date-point>`.
 
-.. versionadded:: 6.3
-
-    The :class:`Symfony\\Component\\Clock\\Clock` class and ``now()`` function
-    were introduced in Symfony 6.3.
-
-.. versionadded:: 6.4
-
-    The ``modifier`` argument of the ``now()`` function was introduced in
-    Symfony 6.4.
-
 Available Clocks Implementations
 --------------------------------
 
@@ -208,10 +194,6 @@ you can set the current time arbitrarily without having to change your service c
 This will help you test every case of your method without the need of actually
 being in a month or another.
 
-.. versionadded:: 6.3
-
-    The :class:`Symfony\\Component\\Clock\\ClockAwareTrait` was introduced in Symfony 6.3.
-
 .. _clock_date-point:
 
 The ``DatePoint`` Class
@@ -253,11 +235,6 @@ The constructor also allows setting a timezone or custom referenced date::
     error handling across versions of PHP, thanks to polyfilling `PHP 8.3's behavior`_
     on the topic.
 
-.. versionadded:: 6.4
-
-    The :class:`Symfony\\Component\\Clock\\DatePoint` class was introduced
-    in Symfony 6.4.
-
 .. _clock_writing-tests:
 
 Writing Time-Sensitive Tests
@@ -314,10 +291,6 @@ By combining the :class:`Symfony\\Component\\Clock\\ClockAwareTrait` and
 :class:`Symfony\\Component\\Clock\\Test\\ClockSensitiveTrait`, you have full
 control on your time-sensitive code's behavior.
 
-.. versionadded:: 6.3
-
-    The :class:`Symfony\\Component\\Clock\\Test\\ClockSensitiveTrait` was introduced in Symfony 6.3.
-
 Exceptions Management
 ---------------------
 
@@ -338,11 +311,6 @@ These exceptions are available starting from PHP 8.3. However, thanks to the
 `symfony/polyfill-php83`_ dependency required by the Clock component, you can
 use them even if your project doesn't use PHP 8.3 yet.
 
-.. versionadded:: 6.4
-
-    The support for ``DateMalformedStringException`` and
-    ``DateInvalidTimeZoneException`` was introduced in Symfony 6.4.
-
 .. _`PSR-20`: https://www.php-fig.org/psr/psr-20/
 .. _`accepted by the DateTime constructor`: https://www.php.net/manual/en/datetime.formats.php
 .. _`PHP DateTime exceptions`: https://wiki.php.net/rfc/datetime-exceptions

diff --git a/components/config/definition.rst b/components/config/definition.rst
@@ -171,11 +171,6 @@ The configuration can now be written like this::
         ->end()
     ;
 
-.. versionadded:: 6.3
-
-    The support of enum values in ``enumNode()`` was introduced
-    in Symfony 6.3.
-
 Array Nodes
 ~~~~~~~~~~~
 

diff --git a/components/console/events.rst b/components/console/events.rst
@@ -156,11 +156,6 @@ Listeners receive a
     a signal. You can learn more about signals in the
     :ref:`the dedicated section <console-events_signal>`.
 
-    .. versionadded:: 6.4
-
-        Dispatching the ``ConsoleEvents::TERMINATE`` event on exit
-        signal was introduced in Symfony 6.4.
-
 .. _console-events_signal:
 
 The ``ConsoleEvents::SIGNAL`` Event
@@ -207,11 +202,6 @@ method::
         $event->abortExit();
     });
 
-.. versionadded:: 6.3
-
-    The ``setExitCode()``, ``getExitCode()`` and ``abortExit()`` methods were introduced
-    in Symfony 6.3.
-
 .. tip::
 
     All the available signals (``SIGINT``, ``SIGQUIT``, etc.) are defined as
@@ -263,21 +253,6 @@ handle all signals e.g. to do some tasks before terminating the command.
     :method:`Symfony\\Component\\Console\\SignalRegistry\\SignalMap::getSignalName`
     method.
 
-    .. versionadded:: 6.4
-
-        The :class:`Symfony\\Component\\Console\\SignalRegistry\\SignalMap` class was
-        introduced in Symfony 6.4.
-
-.. deprecated:: 6.3
-
-    In Symfony versions previous to 6.3, all signals (except ``SIGUSR1`` and
-    ``SIGUSR2``) would terminate the script by calling ``exit(0)``. Starting
-    from Symfony 6.3, no more signal is automatically calling ``exit(0)``.
-
-.. deprecated:: 6.3
-
-    Not returning a value in ``handleSignal()`` is deprecated since Symfony 6.3.
-
 .. _`reserved exit codes`: https://www.tldp.org/LDP/abs/html/exitcodes.html
 .. _`Signals`: https://en.wikipedia.org/wiki/Signal_(IPC)
 .. _`constants of the PCNTL PHP extension`: https://www.php.net/manual/en/pcntl.constants.php