Remove more references to previous versions

Author: javiereguiluz

best_practices.rst

@@ -368,7 +368,7 @@ Use the ``auto`` Password Hasher
 
 The :ref:`auto password hasher <reference-security-encoder-auto>` automatically
 selects the best possible encoder/hasher depending on your PHP installation.
-Starting from Symfony 5.3, the default auto hasher is ``bcrypt``.
+Currently, the default auto hasher is ``bcrypt``.
 
 Use Voters to Implement Fine-grained Security Restrictions
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

components/dependency_injection.rst

@@ -299,12 +299,10 @@ config files:
             $services = $configurator->services();
 
             $services->set('mailer', 'Mailer')
-                // the param() method was introduced in Symfony 5.2.
                 ->args([param('mailer.transport')])
             ;
 
             $services->set('newsletter_manager', 'NewsletterManager')
-                // In versions earlier to Symfony 5.1 the service() function was called ref()
                 ->call('setMailer', [service('mailer')])
             ;
         };

components/runtime.rst

@@ -358,12 +358,6 @@ logic could be versioned as a part of a normal package. If the application
 author decides to use this component, the package maintainer of the Runtime
 class will have more control and can fix bugs and add features.
 
-.. note::
-
-    Before Symfony 5.3, the Symfony bootstrap logic was part of a Flex recipe.
-    Since recipes are rarely updated by users, bug patches would rarely be
-    installed.
-
 The Runtime component is designed to be totally generic and able to run any
 application outside of the global state in 6 steps:
 

components/security/authentication.rst

@@ -130,8 +130,6 @@ password was valid::
     use Symfony\Component\Security\Core\User\InMemoryUserProvider;
     use Symfony\Component\Security\Core\User\UserChecker;
 
-    // The 'InMemoryUser' class was introduced in Symfony 5.3.
-    // In previous versions it was called 'User'
     $userProvider = new InMemoryUserProvider(
         [
             'admin' => [

components/security/secure_tools.rst

@@ -7,9 +7,9 @@ also use them if you want to solve the problem they address.
 
 .. note::
 
-    The functions described in this article were introduced in PHP 5.6 or 7.
-    For older PHP versions, a polyfill is provided by the
-    `Symfony Polyfill Component`_.
+    The functions described in this article are available in modern PHP versions.
+    If your project uses a legacy PHP version, you can use them thanks to some
+    of the polyfills provided by the `Symfony Polyfill Component`_.
 
 Comparing Strings
 ~~~~~~~~~~~~~~~~~

event_dispatcher.rst

@@ -220,8 +220,6 @@ a "main" request or a "sub request"::
     {
         public function onKernelRequest(RequestEvent $event)
         {
-            // The isMainRequest() method was introduced in Symfony 5.3.
-            // In previous versions it was called isMasterRequest()
             if (!$event->isMainRequest()) {
                 // don't do anything if it's not the main request
                 return;

messenger.rst

@@ -1064,8 +1064,8 @@ it in the ``port`` parameter of the DSN (e.g. ``amqps://localhost?cacert=/etc/ss
 
 .. note::
 
-    With Symfony 5.3 or newer, you can limit the consumer of an AMQP transport to only
-    process messages from some queues of an exchange. See :ref:`messenger-limit-queues`.
+    You can limit the consumer of an AMQP transport to only process messages
+    from some queues of an exchange. See :ref:`messenger-limit-queues`.
 
 The transport has a number of other options, including ways to configure
 the exchange, queues binding keys and more. See the documentation on

reference/configuration/security.rst

@@ -125,9 +125,7 @@ This option is explained in detail in :doc:`/security/access_control`.
 hashers
 -------
 
-This option defines the algorithm used to *hash* the password of the users
-(which in previous Symfony versions was wrongly called *"password encoding"*).
-
+This option defines the algorithm used to *hash* the password of the users.
 If your app defines more than one user class, each of them can define its own
 hashing algorithm. Also, each algorithm defines different config options:
 
@@ -320,9 +318,9 @@ hashing algorithm. Also, each algorithm defines different config options:
 Using the "auto" Password Hasher
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-It automatically selects the best available hasher. Starting from Symfony 5.3,
-it uses the Bcrypt hasher. If PHP or Symfony adds new password hashers in the
-future, it might select a different hasher.
+It automatically selects the best available hasher, which currently is the
+Bcrypt hasher. If PHP or Symfony adds new password hashers in the future, it
+might select a different hasher.
 
 Because of this, the length of the hashed passwords may change in the future, so
 make sure to allocate enough space for them to be persisted (``varchar(255)``

reference/configuration/swiftmailer.rst

@@ -211,10 +211,6 @@ delivery_addresses
 
 **type**: ``array``
 
-.. note::
-
-    In previous versions, this option was called ``delivery_address``.
-
 If set, all email messages will be sent to these addresses instead of being sent
 to their actual recipients. This is often useful when developing. For example,
 by setting this in the ``config/packages/dev/swiftmailer.yaml`` file, you can

security.rst

@@ -221,7 +221,7 @@ command will pre-configure this for you:
                 # use your user class name here
                 App\Entity\User:
                     # Use native password hasher, which auto-selects the best
-                    # possible hashing algorithm (starting from Symfony 5.3 this is "bcrypt")
+                    # possible hashing algorithm (which currently is "bcrypt")
                     algorithm: auto
 
     .. code-block:: xml

security/custom_authentication_provider.rst

@@ -216,9 +216,6 @@ the ``PasswordDigest`` header value matches with the user's password::
 
         public function authenticate(TokenInterface $token): WsseUserToken
         {
-            // The loadUserByIdentifier() and getUserIdentifier() methods were
-            // introduced in Symfony 5.3. In previous versions they were called
-            // loadUserByUsername() and getUsername() respectively
             $user = $this->userProvider->loadUserByIdentifier($token->getUserIdentifier());
 
             if ($user && $this->validateDigest($token->digest, $token->nonce, $token->created, $user->getPassword())) {
@@ -439,7 +436,6 @@ to service ids that may not exist yet: ``App\Security\Authentication\Provider\Ws
 
             $services->set(WsseListener::class)
                 ->args([
-                    // In versions earlier to Symfony 5.1 the service() function was called ref()
                     service('security.token_storage'),
                     service('security.authentication.manager'),
                 ])

security/json_login_setup.rst

@@ -84,8 +84,6 @@ The next step is to configure a route in your app matching this path:
                 $user = $this->getUser();
 
                 return $this->json([
-                    // The getUserIdentifier() method was introduced in Symfony 5.3.
-                    // In previous versions it was called getUsername()
                     'username' => $user->getUserIdentifier(),
                     'roles' => $user->getRoles(),
                 ]);

security/user_provider.rst

@@ -135,8 +135,6 @@ interface only requires one method: ``loadUserByIdentifier($identifier)``::
     {
         // ...
 
-        // The loadUserByIdentifier() method was introduced in Symfony 5.3.
-        // In previous versions it was called loadUserByUsername()
         public function loadUserByIdentifier(string $usernameOrEmail): ?User
         {
             $entityManager = $this->getEntityManager();
@@ -231,8 +229,6 @@ users will hash their passwords:
             # ...
             password_hashers:
                 # this internal class is used by Symfony to represent in-memory users
-                # (the 'InMemoryUser' class was introduced in Symfony 5.3.
-                # In previous versions it was called 'User')
                 Symfony\Component\Security\Core\User\InMemoryUser: 'auto'
 
     .. code-block:: xml
@@ -251,8 +247,6 @@ users will hash their passwords:
                 <!-- ... -->
 
                 <!-- this internal class is used by Symfony to represent in-memory users -->
-                <!-- (the 'InMemoryUser' class was introduced in Symfony 5.3.
-                     In previous versions it was called 'User') -->
                 <security:password-hasher class="Symfony\Component\Security\Core\User\InMemoryUser"
                     algorithm="auto"
                 />
@@ -264,8 +258,6 @@ users will hash their passwords:
         // config/packages/security.php
 
         // this internal class is used by Symfony to represent in-memory users
-        // (the 'InMemoryUser' class was introduced in Symfony 5.3.
-        // In previous versions it was called 'User')
         use Symfony\Component\Security\Core\User\InMemoryUser;
         use Symfony\Config\SecurityConfig;
 
@@ -373,9 +365,6 @@ command will generate a nice skeleton to get you started::
     class UserProvider implements UserProviderInterface, PasswordUpgraderInterface
     {
         /**
-         * The loadUserByIdentifier() method was introduced in Symfony 5.3.
-         * In previous versions it was called loadUserByUsername()
-         *
          * Symfony calls this method if you use features like switch_user
          * or remember_me. If you're not using these features, you do not
          * need to implement this method.

service_container.rst

@@ -533,7 +533,6 @@ parameter and in PHP config use the ``service()`` function:
             $services = $configurator->services();
 
             $services->set(MessageGenerator::class)
-                // In versions earlier to Symfony 5.1 the service() function was called ref()
                 ->args([service('logger')])
             ;
         };

service_container/alias_private.rst

@@ -276,7 +276,6 @@ The following example shows how to inject an anonymous service into another serv
             $services = $configurator->services();
 
             $services->set(Foo::class)
-                // In versions earlier to Symfony 5.1 the inline_service() function was called inline()
                 ->args([inline_service(AnonymousBar::class)]);
         };
 

service_container/calls.rst

@@ -73,7 +73,6 @@ To configure the container to call the ``setLogger`` method, use the ``calls`` k
             // ...
 
             $services->set(MessageGenerator::class)
-                // In versions earlier to Symfony 5.1 the service() function was called ref()
                 ->call('setLogger', [service('logger')]);
         };
 

service_container/configurators.rst

@@ -179,7 +179,6 @@ all the classes are already loaded as services. All you need to do is specify th
             $services->load('App\\', '../src/*');
 
             // override the services to set the configurator
-            // In versions earlier to Symfony 5.1 the service() function was called ref()
             $services->set(NewsletterManager::class)
                 ->configurator(service(EmailConfigurator::class), 'configure');
 

service_container/factories.rst

@@ -163,7 +163,6 @@ Configuration of the service container then looks like this:
             // second, use the factory service as the first argument of the 'factory'
             // method and the factory method as the second argument
             $services->set(NewsletterManager::class)
-                // In versions earlier to Symfony 5.1 the service() function was called ref()
                 ->factory([service(NewsletterManagerFactory::class), 'createNewsletterManager']);
         };
 

service_container/injection_types.rst

@@ -78,7 +78,6 @@ service container configuration:
             $services = $configurator->services();
 
             $services->set(NewsletterManager::class)
-                // In versions earlier to Symfony 5.1 the service() function was called ref()
                 ->args(service('mailer'));
         };
 

service_container/optional_dependencies.rst

@@ -42,7 +42,6 @@ if the service does not exist:
             $services = $configurator->services();
 
             $services->set(NewsletterManager::class)
-                // In versions earlier to Symfony 5.1 the service() function was called ref()
                 ->args([service('logger')->nullOnInvalid()]);
         };
 

service_container/parent_services.rst

@@ -128,7 +128,6 @@ avoid duplicated service definitions:
             $services->set(BaseDoctrineRepository::class)
                 ->abstract()
                 ->args([service('doctrine.orm.entity_manager')])
-                // In versions earlier to Symfony 5.1 the service() function was called ref()
                 ->call('setLogger', [service('logger')])
             ;
 

service_container/service_decoration.rst

@@ -172,7 +172,6 @@ automatically changed to ``'.inner'``):
             $services->set(DecoratingMailer::class)
                 ->decorate(Mailer::class)
                 // pass the old service as an argument
-                // In versions earlier to Symfony 5.1 the service() function was called ref()
                 ->args([service('.inner')]);
         };
 

service_container/service_subscribers_locators.rst

@@ -372,7 +372,6 @@ other services. To do so, create a new service definition using the
             $services = $configurator->services();
 
             $services->set('app.command_handler_locator', ServiceLocator::class)
-                // In versions earlier to Symfony 5.1 the service() function was called ref()
                 ->args([[
                     'App\FooCommand' => service('app.command_handler.foo'),
                     'App\BarCommand' => service('app.command_handler.bar'),

translation/debug.rst

@@ -21,9 +21,8 @@ command helps you to find these missing or unused translation messages templates
 
     The extractors can't find messages translated outside templates (like form
     labels or controllers) unless using :ref:`translatable-objects` or calling
-    the ``trans()`` method on a translator (since Symfony 5.3). Dynamic
-    translations using variables or expressions in templates are not
-    detected either:
+    the ``trans()`` method on a translator. Dynamic translations using variables
+    or expressions in templates are not detected either:
 
     .. code-block:: twig