clean up 7.4 versionadded directives

Author: xabbuh

components/config/definition.rst

@@ -743,12 +743,6 @@ of the option name using the second argument of the ``arrayNode()`` method::
         ->end()
     ;
 
-.. versionadded:: 7.4
-
-    The second argument of ``arrayNode()`` was introduced in Symfony 7.4. In prior
-    Symfony versions, you had to define the singular variant using the ``fixXmlConfig()``
-    method on the root node (``$rootNode->fixXmlConfig('extension')``).
-
 This ensures that single XML elements are still turned into an array. So you may have:
 
 .. code-block:: xml

components/runtime.rst

@@ -315,10 +315,6 @@ or a JSON encoded string::
 
     // ...
 
-.. versionadded:: 7.4
-
-    The support for JSON contents in ``APP_RUNTIME_OPTIONS`` was introduced in Symfony 7.4.
-
 You can also configure ``extra.runtime`` in ``composer.json``:
 
 .. code-block:: json

console.rst

@@ -167,11 +167,6 @@ longer help text for the command::
         }
     }
 
-.. versionadded:: 7.4
-
-    The feature to define usage examples in the ``#[AsCommand]`` attribute was
-    introduced in Symfony 7.4.
-
 Additionally, you can extend the :class:`Symfony\\Component\\Console\\Command\\Command` class to
 leverage advanced features like lifecycle hooks (e.g. :method:`Symfony\\Component\\Console\\Command\\Command::initialize` and
 and :method:`Symfony\\Component\\Console\\Command\\Command::interact`)::

lock.rst

@@ -330,8 +330,3 @@ For example, to select the ``invoice`` lock defined earlier::
             // ...
         }
     }
-
-.. versionadded:: 7.4
-
-    Before Symfony 7.4, the target name had to include the ``.lock.factory``
-    suffix (e.g. ``#[Target('invoice.lock.factory')]``).

object_mapper.rst

@@ -447,10 +447,6 @@ With this configuration, ObjectMapper maps each item in the ``products`` array
 according to the usual mapping rules. Without ``transform: new MapCollection()``,
 the array is left unchanged.
 
-.. versionadded:: 7.4
-
-    The ``MapCollection`` transformer was introduced in Symfony 7.4.
-
 Mapping Multiple Targets
 ------------------------
 

reference/configuration/framework.rst

@@ -279,11 +279,6 @@ For example, to select the ``foo_package`` package defined earlier::
         }
     }
 
-.. versionadded:: 7.4
-
-    Before Symfony 7.4, the target name had to include the ``.package``
-    suffix (e.g. ``#[Target('foo_package.package')]``).
-
 .. _reference-framework-assets-packages:
 
 packages

reference/constraints/Url.rst

@@ -243,10 +243,6 @@ The value of this option can also be an asterisk (``*``) to allow all protocols:
     // (e.g. 'https://', 'git+ssh://', 'file://', 'custom://')
     protocols: '*'
 
-.. versionadded:: 7.4
-
-    Support for ``*`` in the ``protocols`` option was introduced in Symfony 7.4.
-
 ``relativeProtocol``
 ~~~~~~~~~~~~~~~~~~~~
 

service_container/service_decoration.rst

@@ -128,11 +128,6 @@ but keeps a reference of the old one as ``.inner``:
     You can apply multiple ``#[AsDecorator]`` attributes to the same class to
     decorate multiple services with it.
 
-    .. versionadded:: 7.4
-
-        The possibility to allow multiple ``#[AsDecorator]`` attributes was
-        introduced in Symfony 7.4.
-
 The ``decorates`` option tells the container that the ``App\DecoratingMailer``
 service replaces the ``App\Mailer`` service. If you're using the
 :ref:`default services.yaml configuration <service-container-services-load-example>`,