use new .. deprecated:: directive

Author: OskarStark

bundles/extension.rst

@@ -130,7 +130,7 @@ read more about it, see the ":doc:`/bundles/configuration`" article.
 Adding Classes to Compile
 -------------------------
 
-.. versionadded:: 3.3
+.. deprecated:: 3.3
 
     This technique is discouraged and the ``addClassesToCompile()`` method was
     deprecated in Symfony 3.3 because modern PHP versions make it unnecessary.

components/console/events.rst

@@ -86,7 +86,7 @@ C/C++ standard.::
 The ``ConsoleEvents::EXCEPTION`` Event
 --------------------------------------
 
-.. versionadded:: 3.3
+.. deprecated:: 3.3
 
     The ``ConsoleEvents::EXCEPTION`` event was deprecated in Symfony 3.3. Use
     the ``ConsoleEvents::ERROR`` event instead.

components/event_dispatcher/container_aware_dispatcher.rst

@@ -4,7 +4,7 @@
 The Container Aware Event Dispatcher
 ====================================
 
-.. versionadded:: 3.3
+.. deprecated:: 3.3
 
     The ``ContainerAwareEventDispatcher`` class has been deprecated in Symfony 3.3
     and it will be removed in Symfony 4.0. Use ``EventDispatcher`` with

components/filesystem/lock_handler.rst

@@ -1,7 +1,7 @@
 LockHandler
 ===========
 
-.. versionadded:: 3.4
+.. deprecated:: 3.4
 
     The ``LockHandler`` class was deprecated in Symfony 3.4 and it will be
     removed in Symfony 4.0. Use :ref:`SemaphoreStore <lock-store-semaphore>`

configuration/external_parameters.rst

@@ -122,7 +122,7 @@ of the following:
 
 .. tip::
 
-    .. versionadded:: 3.3
+    .. deprecated:: 3.3
 
         The support of the special ``SYMFONY__`` environment variables was
         deprecated in Symfony 3.3 and it will be removed in 4.0. Instead of

debug/debugging.rst

@@ -61,7 +61,7 @@ cache files, or you can change the extension used by Symfony for these files::
 
     $kernel->loadClassCache('classes', '.php.cache');
 
-.. versionadded:: 3.3
+.. deprecated:: 3.3
 
     The ``loadClassCache()`` was deprecated in Symfony 3.3 and removed in
     Symfony 4.0. No alternative is provided because this feature is useless

reference/configuration/kernel.rst

@@ -56,7 +56,7 @@ directory and rename it to something else (e.g. ``foo``).
 Root Directory
 ~~~~~~~~~~~~~~
 
-.. versionadded:: 3.3
+.. deprecated:: 3.3
 
     The ``getRootDir()`` method is deprecated since Symfony 3.3. Use the new
     ``getProjectDir()`` method instead.

reference/configuration/security.rst

@@ -500,7 +500,7 @@ Learn more about user checkers in :doc:`/security/user_checkers`.
 HTTP-Digest Authentication
 --------------------------
 
-.. versionadded:: 3.4
+.. deprecated:: 3.4
 
     HTTP-Digest Authentication was deprecated in Symfony 3.4 and it will be
     removed in Symfony 4.0.

reference/configuration/web_profiler.rst

@@ -50,7 +50,7 @@ environment.
 position
 ~~~~~~~~
 
-.. versionadded:: 3.4
+.. deprecated:: 3.4
 
     The ``position`` option was deprecated in Symfony 3.4 and it will be removed
     in Symfony 4.0, where the toolbar is always displayed in the ``bottom`` position.

security.rst

@@ -963,7 +963,7 @@ For more details on expressions and security, see :doc:`/security/expressions`.
 Access Control Lists (ACLs): Securing individual Database Objects
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-.. versionadded:: 3.4
+.. deprecated:: 3.4
 
     ACL support was deprecated in Symfony 3.4 and will be removed in 4.0. Install
     the `Symfony ACL bundle`_ if you want to keep using ACL.

security/acl.rst

@@ -4,7 +4,7 @@
 How to Use Access Control Lists (ACLs)
 ======================================
 
-.. versionadded:: 3.4
+.. deprecated:: 3.4
 
     ACL support was deprecated in Symfony 3.4 and will be removed in 4.0. Install
     the `Symfony ACL bundle`_ if you want to keep using ACL.

security/acl_advanced.rst

@@ -4,7 +4,7 @@
 How to Use advanced ACL Concepts
 ================================
 
-.. versionadded:: 3.4
+.. deprecated:: 3.4
 
     ACL support was deprecated in Symfony 3.4 and will be removed in 4.0. Install
     the `Symfony ACL bundle`_ if you want to keep using ACL.

security/multiple_user_providers.rst

@@ -92,7 +92,7 @@ Now, all firewalls that explicitly define ``chain_provider`` as their user
 provider will, in turn, try to load the user from both the ``in_memory`` and
 ``user_db`` providers.
 
-.. versionadded:: 3.4
+.. deprecated:: 3.4
 
     In previous Symfony versions, firewalls that didn't define their user provider
     explicitly, used the first existing provider (``chain_provider`` in this