Remove old versionadded directives

Author: OskarStark

components/expression_language/syntax.rst

@@ -21,10 +21,6 @@ The component supports:
 * **null** - ``null``
 * **exponential** - also known as scientific (e.g. ``1.99E+3`` or ``1e-2``)
 
-    .. versionadded:: 4.4
-    
-        The ``exponential`` literal was introduced in Symfony 4.4.
-
 .. caution::
 
     A backslash (``\``) must be escaped by 4 backslashes (``\\\\``) in a string

components/http_kernel.rst

@@ -530,18 +530,6 @@ object, which you can use to access the original exception via the
 method. A typical listener on this event will check for a certain type of
 exception and create an appropriate error ``Response``.
 
-.. versionadded:: 4.4
-
-    The :method:`Symfony\\Component\\HttpKernel\\Event\\ExceptionEvent::getThrowable` and
-    :method:`Symfony\\Component\\HttpKernel\\Event\\ExceptionEvent::setThrowable` methods
-    were introduced in Symfony 4.4.
-
-.. deprecated:: 4.4
-
-    The :method:`Symfony\\Component\\HttpKernel\\Event\\ExceptionEvent::getException` and
-    :method:`Symfony\\Component\\HttpKernel\\Event\\ExceptionEvent::setException` methods
-    are deprecated since Symfony 4.4.
-
 For example, to generate a 404 page, you might throw a special type of exception
 and then add a listener on this event that looks for this exception and
 creates and returns a 404 ``Response``. In fact, the HttpKernel component

security/password_migration.rst

@@ -4,10 +4,6 @@
 How to Migrate a Password Hash
 ==============================
 
-.. versionadded:: 4.4
-
-    Password migration was introduced in Symfony 4.4.
-
 In order to protect passwords, it is recommended to store them using the latest
 hash algorithms. This means that if a better hash algorithm is supported on the
 system, the user's password should be rehashed and stored. Symfony provides this
@@ -122,8 +118,8 @@ is available to hash the user's password. If it is, it'll hash the correct
 password using the new hash. You can enable this behavior by implementing how
 this newly hashed password should be stored:
 
-* `When using Doctrine's entity user provider <Upgrade the Password when using Doctrine>`_ 
-* `When using a custom user provider <Upgrade the Password when using a custom User Provider>`_ 
+* `When using Doctrine's entity user provider <Upgrade the Password when using Doctrine>`_
+* `When using a custom user provider <Upgrade the Password when using a custom User Provider>`_
 
 After this, you're done and passwords are always hashed as secure as possible!
 

service_container.rst

@@ -739,10 +739,6 @@ You can also use the ``bind`` keyword to bind specific arguments by name or type
             // ...
         };
 
-.. versionadded:: 4.4
-
-    The feature to bind tagged services was introduced in Symfony 4.4.
-
 By putting the ``bind`` key under ``_defaults``, you can specify the value of *any*
 argument for *any* service defined in this file! You can bind arguments by name
 (e.g. ``$adminEmail``), by type (e.g. ``Psr\Log\LoggerInterface``) or both

workflow.rst

@@ -339,11 +339,6 @@ order:
     The leaving and entering events are triggered even for transitions that stay
     in same place.
 
-.. versionadded:: 4.3
-
-    Following events are also dispatched when the subject enters the workflow
-    for the first time: ``workflow.entered`` and ``workflow.[worflow name].entered``.
-
 Here is an example of how to enable logging for every time a "blog_publishing"
 workflow leaves a place::