Remove mention of CompilerPassInterface support for bundles

Author: MatTheCat

service_container/compiler_passes.rst

@@ -67,37 +67,9 @@ method of the application kernel::
 Working with Compiler Passes in Bundles
 ---------------------------------------
 
-If your compiler pass is relatively small, you can add it directly in the main
-bundle class. To do so, make your bundle implement the
-:class:`Symfony\\Component\\DependencyInjection\\Compiler\\CompilerPassInterface`
-and place the compiler pass code inside the ``process()`` method of the main
-bundle class::
-
-    // src/MyBundle/MyBundle.php
-    namespace App\MyBundle;
-
-    use App\DependencyInjection\Compiler\CustomPass;
-    use Symfony\Component\DependencyInjection\Compiler\CompilerPassInterface;
-    use Symfony\Component\DependencyInjection\ContainerBuilder;
-    use Symfony\Component\HttpKernel\Bundle\AbstractBundle;
-
-    class MyBundle extends AbstractBundle implements CompilerPassInterface
-    {
-        public function process(ContainerBuilder $container): void
-        {
-            // in this method you can manipulate the service container:
-            // for example, changing some container service:
-            $container->getDefinition('app.some_private_service')->setPublic(true);
-
-            // or processing tagged services:
-            foreach ($container->findTaggedServiceIds('some_tag') as $id => $tags) {
-                // ...
-            }
-        }
-    }
-
-Alternatively, when using :ref:`separate compiler pass classes <components-di-separate-compiler-passes>`,
-bundles can enable them in the ``build()`` method of their main bundle class::
+:doc:`Bundles </bundles>` can define compiler passes in the ``build()`` method of
+the main bundle class (this is not needed when implementing the ``process()``
+method in the extension)::
 
     // src/MyBundle/MyBundle.php
     namespace App\MyBundle;