Adding versionadded

weaverryan · weaverryan · commit ee2776566da9 · 2017-05-02T06:59:11.000-04:00
diff --git a/controller.rst b/controller.rst
@@ -149,6 +149,9 @@ and many others that you'll learn about next.
     via ``$this->get()`` or ``$this->container->get()``. This forces you to write
     more robust code to access services, but if you're not use, use ``Controller``.
 
+.. versionadded:: 3.3
+    The ``AbstractController`` class was added in Symfony 3.3.
+
 .. index::
    single: Controller; Redirecting
 
@@ -237,6 +240,10 @@ The Symfony templating system and Twig are explained more in the
 Fetching Services as Arguments
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
+.. versionadded:: 3.3
+    The ability to type-hint an argument in order to receive a service was added
+    in Symfony 3.3.
+
 Symfony comes *packed* with a lot of useful objects, called :doc:`services </service_container>`.
 These are used for rendering templates, sending emails, querying the database and
 any other "work" you can think of.
diff --git a/service_container.rst b/service_container.rst
@@ -43,6 +43,9 @@ service's class or interface name. Want to :doc:`log </logging>` something? No p
         // ...
     }
 
+.. versionadded:: 3.3
+    The ability to type-hint a service in order to receive it was added in Symfony 3.3.
+
 .. _container-debug-container:
 
 What other services are available? Find out by running:
@@ -177,6 +180,10 @@ the service container *how* to instantiate it:
         // app/config/services.php
         // _defaults and loading entire directories is not possible with PHP configuration
 
+.. versionadded:: 3.3
+    The ``_defaults`` key and ability to load services from a directory were added
+    in Symfony 3.3.
+
 That's it! Thanks to the ``AppBundle\`` line and ``resource`` key below it, a service
 will be registered for each class in the ``src/AppBundle/Service`` directory (and
 the other directories listed).
@@ -462,6 +469,11 @@ pass here. No problem! In your configuration, you can explicitly set this argume
             ->setPublic(false)
             ->setArgument('$adminEmail', 'manager@example.com');
 
+.. versionadded:: 3.3
+    The ability to configure an argument by its name (``$adminEmail``) was added
+    in Symfony 3.3. Previously, you could configure it only by its index (``2`` in
+    this case).
+
 Thanks to this, the container will pass ``manager@example.com`` as the third argument
 to ``__construct`` when creating the ``SiteUpdateManager`` service. The other arguments
 will still be autowired.
@@ -641,6 +653,9 @@ service whose id is ``monolog.logger.request``.
 The autoconfigure Option
 ------------------------
 
+.. versionadded:: 3.3
+    The ``autoconfigure`` option was added in Symfony 3.3.
+
 Above, we've set ``autoconfigure: true`` in the ``_defaults`` section so that it
 applies to all services defined in that file. With this setting, the container will
 automatically apply certain configuration to your services, based on your service's
