Remove deprecated directives too

Author: javiereguiluz

components/http_foundation/sessions.rst

@@ -166,14 +166,6 @@ and "Remember Me" login settings or other user based state information.
 :class:`Symfony\\Component\\HttpFoundation\\Session\\Attribute\\AttributeBag`
     This is the standard default implementation.
 
-:class:`Symfony\\Component\\HttpFoundation\\Session\\Attribute\\NamespacedAttributeBag`
-    This implementation allows for attributes to be stored in a structured namespace.
-
-    .. deprecated:: 5.3
-
-        The ``NamespacedAttributeBag`` class is deprecated since Symfony 5.3.
-        If you need this feature, you will have to implement the class yourself.
-
 :class:`Symfony\\Component\\HttpFoundation\\Session\\Attribute\\AttributeBagInterface`
 has the API
 
@@ -242,20 +234,6 @@ So any processing of this might quickly get ugly, even adding a token to the arr
     $tokens['c'] = $value;
     $session->set('tokens', $tokens);
 
-.. deprecated:: 5.3
-
-    The ``NamespacedAttributeBag`` class is deprecated since Symfony 5.3.
-    If you need this feature, you will have to implement the class yourself.
-
-With structured namespacing, the key can be translated to the array
-structure like this using a namespace character (which defaults to ``/``)::
-
-    // ...
-    use Symfony\Component\HttpFoundation\Session\Attribute\NamespacedAttributeBag;
-
-    $session = new Session(new NativeSessionStorage(), new NamespacedAttributeBag());
-    $session->set('tokens/c', $value);
-
 Flash Messages
 ~~~~~~~~~~~~~~
 

components/lock.rst

@@ -123,14 +123,9 @@ they can be decorated with the ``RetryTillSaveStore`` class::
 When the provided store does not implement the
 :class:`Symfony\\Component\\Lock\\BlockingStoreInterface` interface, the
 ``Lock`` class will retry to acquire the lock in a non-blocking way until the
-lock is acquired.
-
-.. deprecated:: 5.2
-
-    As of Symfony 5.2, you don't need to use the ``RetryTillSaveStore`` class
-    anymore. The ``Lock`` class now provides the default logic to acquire locks
-    in blocking mode when the store does not implement the
-    ``BlockingStoreInterface`` interface.
+lock is acquired. However, the ``Lock`` class also provides the default logic to
+acquire locks in blocking mode when the store does not implement the
+``BlockingStoreInterface`` interface.
 
 Expiring Locks
 --------------

components/phpunit_bridge.rst

@@ -407,11 +407,6 @@ times (order matters)::
         }
     }
 
-.. deprecated:: 5.1
-
-    Symfony versions previous to 5.1 also included a ``@expectedDeprecation``
-    annotation to test deprecations, but it was deprecated in favor of the method.
-
 Display the Full Stack Trace
 ----------------------------
 

components/yaml/yaml_format.rst

@@ -124,12 +124,6 @@ Numbers
     # an octal
     0o14
 
-.. deprecated:: 5.1
-
-    In YAML 1.1, octal numbers use the notation ``0...``, whereas in YAML 1.2
-    the notation changes to ``0o...``. Symfony 5.1 added support for YAML 1.2
-    notation and deprecated support for YAML 1.1 notation.
-
 .. code-block:: yaml
 
     # an hexadecimal

deployment/proxies.rst

@@ -81,12 +81,6 @@ and what headers your reverse proxy uses to send information:
             ;
         };
 
-.. deprecated:: 5.2
-
-    In previous Symfony versions, the above example used ``HEADER_X_FORWARDED_ALL``
-    to trust all "X-Forwarded-" headers, but that constant is deprecated since
-    Symfony 5.2 in favor of the individual ``HEADER_X_FORWARDED_*`` constants.
-
 .. caution::
 
     Enabling the ``Request::HEADER_X_FORWARDED_HOST`` option exposes the

reference/configuration/framework.rst

@@ -1521,12 +1521,7 @@ or ``null`` might be preferred in production.
 utf8
 ....
 
-**type**: ``boolean`` **default**: ``false``
-
-.. deprecated:: 5.1
-
-    Not setting this option is deprecated since Symfony 5.1. Moreover, the
-    default value of this option will change to ``true`` in Symfony 6.0.
+**type**: ``boolean`` **default**: ``true``
 
 When this option is set to ``true``, the regular expressions used in the
 :ref:`requirements of route parameters <routing-requirements>` will be run

reference/configuration/security.rst

@@ -628,8 +628,6 @@ The ``invalidate_session`` option allows to redefine this behavior. Set this
 option to ``false`` in every firewall and the user will only be logged out from
 the current firewall and not the other ones.
 
-.. _reference-security-logout-success-handler:
-
 ``path``
 ~~~~~~~~
 
@@ -647,23 +645,6 @@ The relative path (if the value starts with ``/``), or absolute URL (if it
 starts with ``http://`` or ``https://``) or the route name (otherwise) to
 redirect after logout.
 
-success_handler
-~~~~~~~~~~~~~~~
-
-.. deprecated:: 5.1
-
-    This option is deprecated since Symfony 5.1. Register an
-    :doc:`event listener </event_dispatcher>` on the
-    :class:`Symfony\\Component\\Security\\Http\\Event\\LogoutEvent`
-    instead.
-
-**type**: ``string`` **default**: ``'security.logout.success_handler'``
-
-The service ID used for handling a successful logout. The service must implement
-:class:`Symfony\\Component\\Security\\Http\\Logout\\LogoutSuccessHandlerInterface`.
-
-If it is set, the logout ``target`` option will be ignored.
-
 .. _reference-security-logout-csrf:
 
 csrf_parameter

reference/constraints/Length.rst

@@ -129,26 +129,6 @@ and ``50``, you might add the following:
 Options
 -------
 
-``allowEmptyString``
-~~~~~~~~~~~~~~~~~~~~
-
-**type**: ``boolean``  **default**: ``false``
-
-.. deprecated:: 5.2
-
-    The ``allowEmptyString`` option is deprecated since Symfony 5.2. If you
-    want to allow empty strings too, combine the ``Length`` constraint with
-    the :doc:`Blank constraint </reference/constraints/Blank>` inside the
-    :doc:`AtLeastOneOf constraint </reference/constraints/AtLeastOneOf>`.
-
-If set to ``true``, empty strings are considered valid (which is the same
-behavior as previous Symfony versions). The default ``false`` value considers
-empty strings not valid.
-
-.. caution::
-
-    This option does not have any effect when no minimum length is given.
-
 ``charset``
 ~~~~~~~~~~~
 

reference/dic_tags.rst

@@ -496,12 +496,7 @@ the :class:`Symfony\\Component\\HttpKernel\\CacheWarmer\\CacheWarmerInterface` i
 The ``warmUp()`` method must return an array with the files and classes to
 preload. Files must be absolute paths and classes must be fully-qualified class
 names. The only restriction is that files must be stored in the cache directory.
-If you don't need to preload anything, return an empty array
-
-.. deprecated:: 5.1
-
-    Not returning an array from the ``warmUp()`` method with the files to
-    preload is deprecated since Symfony 5.1.
+If you don't need to preload anything, return an empty array.
 
 The ``isOptional()`` method should return true if it's possible to use the
 application without calling this cache warmer. In Symfony, optional warmers

reference/forms/types/integer.rst

@@ -88,12 +88,6 @@ is a constant on the :phpclass:`NumberFormatter` class:
   "nearest neighbor". If both neighbors are equidistant, round up. It rounds
   ``2.5`` to ``3``, ``1.6`` and ``1.5`` to ``2`` and ``1.4`` to ``1``.
 
-.. deprecated:: 5.1
-
-    In Symfony versions prior to 5.1, these constants were also defined as aliases
-    in the :class:`Symfony\\Component\\Form\\Extension\\Core\\DataTransformer\\NumberToLocalizedStringTransformer`
-    class, but they are now deprecated in favor of the :phpclass:`NumberFormatter` constants.
-
 Overridden Options
 ------------------