symfony
diff --git a/‎bundles/best_practices.rst
Copy file name to clipboardExpand all lines: bundles/best_practices.rst
+9-11Lines changed: 9 additions & 11 deletions b/‎bundles/best_practices.rst
Copy file name to clipboardExpand all lines: bundles/best_practices.rst
+9-11Lines changed: 9 additions & 11 deletions
diff --git a/‎reference/configuration/framework.rst
Copy file name to clipboardExpand all lines: reference/configuration/framework.rst
+14-14Lines changed: 14 additions & 14 deletions b/‎reference/configuration/framework.rst
Copy file name to clipboardExpand all lines: reference/configuration/framework.rst
+14-14Lines changed: 14 additions & 14 deletions
@@ -195,25 +195,24 @@ Continuous Integration
 
 Testing bundle code continuously, including all its commits and pull requests,
 is a good practice called Continuous Integration. There are several services
-providing this feature for free for open source projects, like `GitHub Actions`_
-and `Travis CI`_.
+providing this feature for free for open source projects, like `GitHub Actions`_.
 
 A bundle should at least test:
 
 * The lower bound of their dependencies (by running ``composer update --prefer-lowest``);
 * The supported PHP versions;
-* All supported major Symfony versions (e.g. both ``4.x`` and ``5.x`` if
+* All supported major Symfony versions (e.g. both ``6.4`` and ``7.x`` if
   support is claimed for both).
 
-Thus, a bundle supporting PHP 7.3, 7.4 and 8.0, and Symfony 4.4 and 5.x should
+Thus, a bundle supporting PHP 7.4, 8.3 and 8.4, and Symfony 6.4 and 7.x should
 have at least this test matrix:
 
 ===========  ===============  ===================
 PHP version  Symfony version  Composer flags
 ===========  ===============  ===================
-7.3          ``4.*``          ``--prefer-lowest``
-7.4          ``5.*``
-8.0          ``5.*``
+7.4          ``6.4``          ``--prefer-lowest``
+8.3          ``7.*``
+8.4          ``7.*``
 ===========  ===============  ===================
 
 .. tip::
@@ -233,10 +232,10 @@ with Symfony Flex to install a specific Symfony version:
 
 .. code-block:: bash
 
-    # this requires Symfony 5.x for all Symfony packages
-    export SYMFONY_REQUIRE=5.*
+    # this requires Symfony 6.x for all Symfony packages
+    export SYMFONY_REQUIRE=6.*
     # alternatively you can run this command to update composer.json config
-    # composer config extra.symfony.require "5.*"
+    # composer config extra.symfony.require "6.*"
 
     # install Symfony Flex in the CI environment
     composer global config --no-plugins allow-plugins.symfony/flex true
@@ -568,4 +567,3 @@ Learn more
 .. _`choose any license`: https://choosealicense.com/
 .. _`valid license identifier`: https://spdx.org/licenses/
 .. _`GitHub Actions`: https://docs.github.com/en/free-pro-team@latest/actions
-.. _`Travis CI`: https://docs.travis-ci.com/
@@ -1250,7 +1250,7 @@ allow_reload
 
 Specifies whether the client can force a cache reload by including a
 Cache-Control "no-cache" directive in the request. Set it to ``true``
-for compliance with RFC 2616. (default: false)
+for compliance with RFC 2616.
 
 allow_revalidate
 ................
@@ -1259,7 +1259,7 @@ allow_revalidate
 
 Specifies whether the client can force a cache revalidate by including a
 Cache-Control "max-age=0" directive in the request. Set it to ``true``
-for compliance with RFC 2616. (default: false)
+for compliance with RFC 2616.
 
 debug
 .....
@@ -1272,11 +1272,11 @@ try to carry on and deliver a meaningful response.
 default_ttl
 ...........
 
-**type**: ``integer``
+**type**: ``integer`` **default**: ``0``
 
 The number of seconds that a cache entry should be considered fresh when no
 explicit freshness information is provided in a response. Explicit
-Cache-Control or Expires headers override this value. (default: 0)
+Cache-Control or Expires headers override this value.
 
 enabled
 .......
@@ -1286,11 +1286,11 @@ enabled
 private_headers
 ...............
 
-**type**: ``array``
+**type**: ``array`` **default**: ``['Authorization', 'Cookie']``
 
 Set of request headers that trigger "private" cache-control behavior on responses
 that don't explicitly state whether the response is public or private via a
-Cache-Control directive. (default: Authorization and Cookie)
+Cache-Control directive.
 
 skip_response_headers
 .....................
@@ -1303,30 +1303,30 @@ and public.
 stale_if_error
 ..............
 
-**type**: ``integer``
+**type**: ``integer`` **default**: ``60``
 
 Specifies the default number of seconds (the granularity is the second) during
-which the cache can serve a stale response when an error is encountered
-(default: 60). This setting is overridden by the stale-if-error HTTP
+which the cache can serve a stale response when an error is encountered.
+This setting is overridden by the stale-if-error HTTP
 Cache-Control extension (see RFC 5861).
 
 stale_while_revalidate
 ......................
 
-**type**: ``integer``
+**type**: ``integer`` **default**: ``2``
 
 Specifies the default number of seconds (the granularity is the second as the
 Response TTL precision is a second) during which the cache can immediately return
-a stale response while it revalidates it in the background (default: 2).
+a stale response while it revalidates it in the background.
 This setting is overridden by the stale-while-revalidate HTTP Cache-Control
 extension (see RFC 5861).
 
 trace_header
 ............
 
-**type**: ``string``
+**type**: ``string`` **default**: ``'X-Symfony-Cache'``
 
-Header name to use for traces. (default: X-Symfony-Cache)
+Header name to use for traces.
 
 trace_level
 ...........
@@ -1335,7 +1335,7 @@ trace_level
 
 For 'short', a concise trace of the main request will be added as an HTTP header.
 'full' will add traces for all requests (including ESI subrequests).
-(default: 'full' if in debug; 'none' otherwise)
+(default: ``'full'`` if in debug; ``'none'`` otherwise)
 
 .. _reference-http-client: