Removed the versionadded directives for previous versions

Author: javiereguiluz

components/browser_kit.rst

@@ -91,9 +91,6 @@ make AJAX requests::
     // the required HTTP_X_REQUESTED_WITH header is added automatically
     $crawler = $client->xmlHttpRequest('GET', '/');
 
-.. versionadded:: 4.1
-    The ``xmlHttpRequest()`` method was introduced in Symfony 4.1.
-
 Clicking Links
 ~~~~~~~~~~~~~~
 

components/cache/cache_pools.rst

@@ -151,10 +151,6 @@ when all items are successfully deleted)::
         # clears the "cache.validation" and "cache.app" pool
         $ php bin/console cache:pool:clear cache.validation cache.app
 
-.. versionadded:: 4.1
-
-    The ``cache:pool:delete`` command was introduced in Symfony 4.1.
-
 .. _component-cache-cache-pool-prune:
 
 Pruning Cache Items

components/config/definition.rst

@@ -791,9 +791,6 @@ for the node, instead of the node's original value.
 Configuring the Node Path Separator
 -----------------------------------
 
-.. versionadded:: 4.1
-    The option to configure the node path separator was introduced in Symfony 4.1.
-
 Consider the following config builder example::
 
     $treeBuilder = new TreeBuilder('database');

components/console/helpers/progressbar.rst

@@ -64,9 +64,6 @@ value and then call the ``setMaxSteps()`` method to update it as needed::
     // a complex task has just been created: increase the progressbar to 200 units
     $progressBar->setMaxSteps(200);
 
-.. versionadded:: 4.1
-    The ``setMaxSteps()`` method was introduced in Symfony 4.1.
-
 Another solution is to omit the steps argument when creating the
 :class:`Symfony\\Component\\Console\\Helper\\ProgressBar` instance::
 
@@ -348,10 +345,6 @@ of the custom placeholders::
 Displaying Multiple Progress Bars
 ---------------------------------
 
-.. versionadded:: 4.1
-    The feature to display multiple progress bars using output sections was
-    introduced in Symfony 4.1.
-
 When using :ref:`Console output sections <console-output-sections>` it's
 possible to display multiple progress bars at the same time and change their
 progress independently::

components/console/helpers/table.rst

@@ -213,9 +213,6 @@ which outputs:
     │ 80-902734-1-6 │ And Then There Were None │ Agatha Christie  │
     └───────────────┴──────────────────────────┴──────────────────┘
 
-.. versionadded:: 4.1
-    The ``box`` style was introduced in Symfony 4.1.
-
 You can also set the style to ``box-double``::
 
     $table->setStyle('box-double');
@@ -234,9 +231,6 @@ which outputs:
     ║ 80-902734-1-6 │ And Then There Were None │ Agatha Christie  ║
     ╚═══════════════╧══════════════════════════╧══════════════════╝
 
-.. versionadded:: 4.1
-    The ``box-double`` style was introduced in Symfony 4.1.
-
 If the built-in styles do not fit your need, define your own::
 
     use Symfony\Component\Console\Helper\TableStyle;
@@ -266,17 +260,6 @@ Here is a full list of things you can customize:
 *  :method:`Symfony\\Component\\Console\\Helper\\TableStyle::setBorderFormat`
 *  :method:`Symfony\\Component\\Console\\Helper\\TableStyle::setPadType`
 
-.. versionadded:: 4.1
-    The ``setDefaultCrossingChars`` method was introduced in Symfony 4.1.
-    It replaces the deprecated ``setHorizontalBorderChar`` method.
-
-    Also, the ``setVerticalBorderChars`` method was introduced. Use this instead
-    of the deprecated ``setVerticalBorderChar`` method.
-
-    The ``setCrossingChars()`` and ``setDefaultCrossingChar()`` methods are also
-    new. Previously you could only use the now deprecated ``setCrossingChar()``
-    method.
-
 .. tip::
 
     You can also register a style globally::
@@ -382,9 +365,6 @@ you to create any table layout you may wish.
 Modifying Rendered Tables
 -------------------------
 
-.. versionadded:: 4.1
-    The feature to modify rendered tables was introduced in Symfony 4.1.
-
 The ``render()`` method requires passing the entire table contents. However,
 sometimes that information is not available beforehand because it's generated
 dynamically. In those cases, use the

components/http_foundation.rst

@@ -242,18 +242,9 @@ the
 method tells you if the request contains a session which was started in one of
 the previous requests.
 
-.. versionadded:: 4.1
-    Using :method:`Symfony\\Component\\HttpFoundation\\Request::getSession`
-    when no session has been set was deprecated in Symfony 4.1. It will throw
-    an exception in Symfony 5.0 when the session is ``null``. Check for an existing session
-    first by calling :method:`Symfony\\Component\\HttpFoundation\\Request::hasSession`.
-
 Processing HTTP Headers
 ~~~~~~~~~~~~~~~~~~~~~~~
 
-.. versionadded:: 4.1
-    The ``HeaderUtils`` class was introduced in Symfony 4.1.
-
 Processing HTTP headers is not a trivial task because of the escaping and white
 space handling of their contents. Symfony provides a
 :class:`Symfony\\Component\\HttpFoundation\\HeaderUtils` class that abstracts
@@ -325,10 +316,6 @@ are also supported::
     $quality = $accept->get('text/xml')->getQuality(); // $quality = 0.8
     $quality = $accept->get('application/xml')->getQuality(); // $quality = 0.3
 
-.. versionadded:: 4.1
-    The support of default values in the ``Accept-*`` headers was introduced in
-    Symfony 4.1.
-
 Accessing other Data
 ~~~~~~~~~~~~~~~~~~~~
 

components/http_foundation/session_configuration.rst

@@ -91,9 +91,6 @@ Example usage::
 Migrating Between Save Handlers
 -------------------------------
 
-.. versionadded:: 4.1
-    The ``MigratingSessionHandler`` class was introduced in Symfony 4.1.
-
 If your application changes the way sessions are stored, use the
 :class:`Symfony\\Component\\HttpFoundation\\Session\\Storage\\Handler\\MigratingSessionHandler`
 to migrate between old and new save handlers without losing session data.

components/ldap.rst

@@ -168,9 +168,5 @@ operation type.
 
 .. versionadded:: 4.2
     The ``applyOperations()`` method was introduced in Symfony 4.2.
-    
-.. versionadded:: 4.1
-    The ``addAttributeValues()`` and ``removeAttributeValues()`` methods
-    were introduced in Symfony 4.1.
 
 .. _Packagist: https://packagist.org/packages/symfony/ldap

components/lock.rst

@@ -157,10 +157,6 @@ to reset the TTL to its original value::
         // refresh the lock for 600 seconds (next refresh() call will be 30 seconds again)
         $lock->refresh(600);
 
-    .. versionadded:: 4.1
-        The feature to pass a custom TTL as an argument of the ``refresh()``
-        method was introduced in Symfony 4.1.
-
 Available Stores
 ----------------
 

components/process.rst

@@ -461,9 +461,6 @@ whether `TTY`_ is supported on the current operating system::
 
     $process = (new Process())->setTty(Process::isTtySupported());
 
-.. versionadded:: 4.1
-    The ``isTtySupported()`` method was introduced in Symfony 4.1.
-
 .. _`Symfony Issue#5759`: https://github.com/symfony/symfony/issues/5759
 .. _`PHP Bug#39992`: https://bugs.php.net/bug.php?id=39992
 .. _`exec`: https://en.wikipedia.org/wiki/Exec_(operating_system)

components/property_info.rst

@@ -249,11 +249,6 @@ for getter/isser/setter/hasser method in addition to whether or not a property i
 to determine if it's accessible. This based on how the :doc:`PropertyAccess </components/property_access>`
 works.
 
-.. versionadded:: 4.1
-
-    The support of hasser methods in the ``ReflectionExtractor`` class was
-    introduced in Symfony 4.1.
-
 .. _property-info-initializable:
 
 Property Initializable Information

components/serializer.rst

@@ -717,10 +717,6 @@ There are several types of normalizers available:
     :class:`Symfony\\Component\\Validator\\ConstraintViolationListInterface`
     into a list of errors according to the `RFC 7807`_ standard.
 
-    .. versionadded:: 4.1
-
-        The ``ConstraintViolationListNormalizer`` was introduced in Symfony 4.1.
-
 .. _component-serializer-encoders:
 
 Encoders
@@ -776,10 +772,8 @@ The ``CsvEncoder`` encodes to and decodes from CSV.
 You can pass the context key ``as_collection`` in order to have the results
 always as a collection.
 
-.. versionadded:: 4.1
-    The ``as_collection`` option was introduced in Symfony 4.1.
-
 .. versionadded:: 4.2
+
     Relying on the default value ``false`` is deprecated since Symfony 4.2.
 
 The ``XmlEncoder``
@@ -818,9 +812,6 @@ the key  ``#comment`` for encoding XML comments::
 You can pass the context key ``as_collection`` in order to have the results
 always as a collection.
 
-.. versionadded:: 4.1
-    The ``as_collection`` option was introduced in Symfony 4.1.
-
 .. tip::
 
     XML comments are ignored by default when decoding contents, but this
@@ -831,9 +822,6 @@ always as a collection.
     changed with the optional ``$encoderIgnoredNodeTypes`` argument of the
     ``XmlEncoder`` class constructor.
 
-    .. versionadded:: 4.1
-        XML comments are ignored by default starting from Symfony 4.1.
-
 The ``YamlEncoder``
 ~~~~~~~~~~~~~~~~~~~
 
@@ -1105,10 +1093,8 @@ having unique identifiers::
     );
     */
 
-.. versionadded:: 4.1
-    The ``setMaxDepthHandler()`` method was introduced in Symfony 4.1.
-
 .. versionadded:: 4.2
+
     The ``$outerObject``, ``$attributeName``, ``$format`` and ``$context``
     parameters of ``setMaxDepthHandler()`` were introduced in Symfony 4.2.
 
@@ -1228,9 +1214,6 @@ These are the options available:
 Handling Constructor Arguments
 ------------------------------
 
-.. versionadded:: 4.1
-    The ``default_constructor_arguments`` option was introduced in Symfony 4.1.
-
 If the class constructor defines arguments, as usually happens with
 `Value Objects`_, the serializer won't be able to create the object if some
 arguments are missing. In those cases, use the ``default_constructor_arguments``

components/var_dumper.rst

@@ -97,17 +97,11 @@ current PHP SAPI:
     function. This function dumps the variables using ``dump()`` and
     immediately ends the execution of the script (using :phpfunction:`exit`).
 
-    .. versionadded:: 4.1
-        The ``dd()`` helper method was introduced in Symfony 4.1.
-
 .. _var-dumper-dump-server:
 
 The Dump Server
 ---------------
 
-.. versionadded:: 4.1
-    The dump server was introduced in Symfony 4.1.
-
 The ``dump()`` function outputs its contents in the same browser window or
 console terminal as your own application. Sometimes mixing the real output
 with the debug output can be confusing. That's why this component provides a
@@ -280,10 +274,6 @@ Example::
         }
     }
 
-.. versionadded:: 4.1
-    The possibility of passing non-string variables as the first argument of
-    ``assertDumpEquals()`` was introduced in Symfony 4.1.
-
 Dump Examples and Output
 ------------------------
 

components/workflow.rst

@@ -75,10 +75,6 @@ are trying to use it with::
     $registry->addWorkflow($blogWorkflow, new InstanceOfSupportStrategy(BlogPost::class));
     $registry->addWorkflow($newsletterWorkflow, new InstanceOfSupportStrategy(Newsletter::class));
 
-.. versionadded:: 4.1
-    The ``addWorkflow()`` method was introduced in Symfony 4.1. In previous
-    Symfony versions it was called ``add()``.
-
 Usage
 -----
 

configuration/external_parameters.rst

@@ -411,9 +411,6 @@ Symfony provides the following env var processors:
         framework:
            trusted_hosts: '%env(csv:TRUSTED_HOSTS)%'
 
-    .. versionadded:: 4.1
-        The ``csv`` processor was introduced in Symfony 4.1.
-
 ``env(file:FOO)``
     Returns the contents of a file whose path is the value of the ``FOO`` env var:
 

console.rst

@@ -37,7 +37,7 @@ want a command to create a user::
     {
         // the name of the command (the part after "bin/console")
         protected static $defaultName = 'app:create-user';
-        
+
         protected function configure()
         {
             // ...
@@ -149,10 +149,6 @@ the console::
         $output->write('create a user.');
     }
 
-.. versionadded:: 4.1
-    The support of PHP iterators in the ``write()`` and ``writeln()`` methods
-    was introduced in Symfony 4.1.
-
 Now, try executing the command:
 
 .. code-block:: terminal
@@ -169,9 +165,6 @@ Now, try executing the command:
 Output Sections
 ~~~~~~~~~~~~~~~
 
-.. versionadded:: 4.1
-    Output sections were introduced in Symfony 4.1.
-
 The regular console output can be divided into multiple independent regions
 called "output sections". Create one or more of these sections when you need to
 clear and overwrite the output information.

controller.rst

@@ -276,10 +276,6 @@ the argument by its name:
 Like with all services, you can also use regular :ref:`constructor injection <services-constructor-injection>`
 in your controllers.
 
-.. versionadded:: 4.1
-    The ability to bind scalar values to controller arguments was introduced in
-    Symfony 4.1. Previously you could only bind services.
-
 For more information about services, see the :doc:`/service_container` article.
 
 Generating Controllers

controller/upload_file.rst

@@ -190,6 +190,7 @@ There are some important things to consider in the code of the above controller:
    method to let Symfony guess the right extension according to the file MIME type;
 
 .. versionadded:: 4.1
+
     The :method:`Symfony\\Component\\HttpFoundation\\File\\UploadedFile::getClientSize`
     method was deprecated in Symfony 4.1 and will be removed in Symfony 5.0.
     Use ``getSize()`` instead.
@@ -267,9 +268,6 @@ logic to a separate service::
     :class:`Symfony\\Component\\HttpFoundation\\File\\Exception\\NoTmpDirFileException`,
     and :class:`Symfony\\Component\\HttpFoundation\\File\\Exception\\PartialFileException`.
 
-    .. versionadded:: 4.1
-        The detailed exception classes were introduced in Symfony 4.1.
-
 Then, define a service for this class:
 
 .. configuration-block::

event_dispatcher.rst

@@ -119,10 +119,6 @@ listener class:
    method (which makes event listeners invokable);
 #. If the ``_invoke()`` method is not defined either, throw an exception.
 
-.. versionadded:: 4.1
-    The support of the ``__invoke()`` method to create invokable event listeners
-    was introduced in Symfony 4.1.
-
 .. note::
 
     There is an optional attribute for the ``kernel.event_listener`` tag called

http_cache.rst

@@ -380,9 +380,6 @@ Symfony won't modify it::
 
     $response->headers->set(AbstractSessionListener::NO_AUTO_CACHE_CONTROL_HEADER, 'true');
 
-.. versionadded:: 4.1
-    The ``NO_AUTO_CACHE_CONTROL_HEADER`` header was introduced in Symfony 4.1.
-
 Summary
 -------
 

logging/monolog_exclude_http_codes.rst

@@ -6,10 +6,6 @@
 How to Configure Monolog to Exclude Specific HTTP Codes from the Log
 ====================================================================
 
-.. versionadded:: 4.1
-    The ability to exclude log messages based on their status codes was
-    introduced in Symfony 4.1 and MonologBundle 3.3.
-
 Sometimes your logs become flooded with unwanted HTTP errors, for example,
 403s and 404s. When using a ``fingers_crossed`` handler, you can exclude
 logging these HTTP codes based on the MonologBundle configuration: