Updating prepend extension capabilities

Author: yceruto

bundles/prepend_extension.rst

@@ -154,7 +154,7 @@ registered and the ``entity_manager_name`` setting for ``acme_hello`` is set to
 Prepending Extension in the Bundle Class
 ----------------------------------------
 
-You can also append or prepend extension configuration directly in your
+You can also prepend extension configuration directly in your
 Bundle class if you extend from the :class:`Symfony\\Component\\HttpKernel\\Bundle\\AbstractBundle`
 class and define the :method:`Symfony\\Component\\HttpKernel\\Bundle\\AbstractBundle::prependExtension`
 method::
@@ -172,12 +172,7 @@ method::
                 'cache' => ['prefix_seed' => 'foo/bar'],
             ]);
 
-            // append
-            $containerConfigurator->extension('framework', [
-                'cache' => ['prefix_seed' => 'foo/bar'],
-            ]);
-
-            // append from file
+            // prepend config from a file
             $containerConfigurator->import('../config/packages/cache.php');
         }
     }
@@ -186,6 +181,12 @@ method::
 
     The ``prependExtension()`` method, like ``prepend()``, is called only at compile time.
 
+.. versionadded:: 7.1
+
+    The :method:`Symfony\\Component\\DependencyInjection\\Loader\\Configurator\\ContainerConfigurator::import`
+    method behavior was modified in Symfony 7.1 to prepend config instead of appending. This behavior change is
+    valid only in the ``prependExtension()`` scope.
+
 Alternatively, you can use the ``prepend`` parameter of the
 :method:`Symfony\\Component\\DependencyInjection\\Loader\\Configurator\\ContainerConfigurator::extension`
 method::