[TASK] Remove or replace TYPO3 12.4 version hints (TYPO3-Documentatio…

…n#4828)

Releases: main

Documentation/ApiOverview/Backend/BackendModules/SudoMode.rst

@@ -42,10 +42,6 @@ invocations.
 Custom backend modules requiring the sudo mode
 ==============================================
 
-..  versionadded:: 12.4
-    With TYPO3 v12.4 sudo mode has been changed to a generic configuration for
-    backend routes (and implicitly modules).
-
 In general, the configuration for a particular route or module looks like this:
 
 ..  code-block:: diff

Documentation/ApiOverview/Backend/BackendRouting.rst

@@ -146,9 +146,8 @@ Example within a controller (we use here a non-Extbase controller):
 Sudo mode
 =========
 
-..  versionadded:: 12.4
-    Starting with TYPO3 v12.4 a the sudo mode, like for the install tool,
-    can be request for arbitrary backend modules.
+The sudo mode, as known from the install tool,
+can be request for arbitrary backend modules.
 
 You can configure the sudo mode in your backend routing like this:
 

Documentation/ApiOverview/CachingFramework/Architecture/Index.rst

@@ -241,8 +241,6 @@ The following caches exist in the TYPO3 Core:
     *   Cache for :ref:`TypoScript <t3tsref:start>`.
 
 `database_schema`
-    .. versionadded:: 12.4.2
-
     **group**: system
 
     Cache for database schema information.

Documentation/ApiOverview/CommandControllers/Tutorial.rst

@@ -32,9 +32,9 @@ This command can be found in the
 1. Register the command
 -----------------------
 
-..  versionadded:: 12.4.8
+..  note::
     The Symfony PHP attribute :php:`\Symfony\Component\Console\Attribute\AsCommand`
-    is now accepted to register console commands.
+    registers console commands.
     See the section :ref:`console-command-tutorial-registration-attribute`
     for more details.
 
@@ -156,8 +156,6 @@ succeeded.
 Use the PHP attribute to register commands
 ==========================================
 
-..  versionadded:: 12.4.8
-
 CLI commands can be registered by setting the attribute
 :php:`\Symfony\Component\Console\Attribute\AsCommand` on the command class.
 When using this attribute there is no need to register the command in the

Documentation/ApiOverview/ContentSecurityPolicy/Index.rst

@@ -42,7 +42,7 @@ the feature flags
 *   :confval:`globals-typo3-conf-vars-sys-features-security-frontend-enforceContentSecurityPolicy`
     (for enforcing)
 *   :confval:`globals-typo3-conf-vars-sys-features-security-frontend-reportContentSecurityPolicy`
-    (for report-only mode, available since TYPO3 v12.4.20)
+    (for report-only mode)
 
 need to be enabled.
 
@@ -127,8 +127,6 @@ used to declare policies for a specific site, for example:
 Disable CSP for a site
 ~~~~~~~~~~~~~~~~~~~~~~
 
-..  versionadded:: 12.4.20
-
 The Content Security Policy for a particular site can be disabled with the
 :yaml:`active` key set to :yaml:`false`:
 

Documentation/ApiOverview/DependencyInjection/Index.rst

@@ -604,8 +604,6 @@ An :php:`Error` is thrown on missing dependency injection for
 Installation-wide configuration
 -------------------------------
 
-..  versionadded:: 12.1
-
 One can set up a global service configuration for a project that can be used in
 multiple project-specific extensions. For example, this way you can alias an
 interface with a concrete implementation that can be used in several extensions.

Documentation/ApiOverview/Events/Events/Core/Security/PolicyMutatedEvent.rst

@@ -6,8 +6,6 @@
 PolicyMutatedEvent
 ==================
 
-..  versionadded:: 12.3
-
 ..  versionchanged:: 12.4.17 | 13.2
     The event also provides the current PSR-7 :php:`\Psr\Http\Message\ServerRequestInterface`
     for additional context

Documentation/ApiOverview/Events/Events/Impexp/BeforeImportEvent.rst

@@ -18,7 +18,4 @@ Example
 API
 ===
 
-..  versionadded:: 12.4.10
-    The method :php:`getFile()` has been added.
-
 ..  include:: /CodeSnippets/Events/Impexp/BeforeImportEvent.rst.txt

Documentation/ApiOverview/Events/Events/SEO/ModifyUrlForCanonicalTagEvent.rst

@@ -11,9 +11,6 @@ With the PSR-14 event `\TYPO3\CMS\Seo\Event\ModifyUrlForCanonicalTagEvent`
 the URL for the :html:`href` attribute of the canonical tag can be altered or
 emptied.
 
-..  versionadded:: 12.4.9
-    The methods :php:`getRequest()` and :php:`getPage()` have been added.
-
 ..  versionchanged:: 13.0
     The event is being dispatched after the standard functionality has been
     executed, such as fetching the URL from the page properties. Effectively,

Documentation/ApiOverview/Fal/Administration/Storages.rst

@@ -54,8 +54,6 @@ Is online?
         which is publicly available. The files will still be available to anyone
         who knows the path to the file.
 
-    ..  versionchanged:: 11.5.35/12.4.11
-
     Assuming that a web project is located in the directory
     :file:`/var/www/example.org/` (the "project root path" for Composer-based
     projects) and the publicly accessible directory is located at

Documentation/ApiOverview/FormEngine/Overview/Index.rst

@@ -50,14 +50,6 @@ In code, this basic workflow looks like this:
     :language: php
     :caption: EXT:my_extension/Classes/SomeClass.php
 
-..  deprecated:: 12.4
-    Using the FormEngine data provider to render records without passing the
-    current :ref:`request object <typo3-request>` is deprecated. Additionally,
-    when instantiating the backend FormEngine-related :php:`FormDataCompiler`,
-    the constructor argument :php:`FormDataGroupInterface` should be omitted,
-    the form data group should be provided as second argument to :php:`compile()`
-    instead. Failing to do so will stop working with TYPO3 v13.
-
 This basically means the main FormEngine concept is a two-fold process: First create an array to gather all
 render-relevant information, then call the render engine using this array to come up with output.
 

Documentation/ApiOverview/Localization/TranslationServer/Crowdin/OnlineTranslation.rst

@@ -179,7 +179,7 @@ FAQ
 ===
 
 
-Should I localize both 12.4 and main?
+Should I localize both 13.4 and main?
 ---------------------------------------
 
 The main branch is the leading version. Any string that is also present in the

Documentation/ApiOverview/RequestLifeCycle/RequestAttributes/CurrentContentObject.rst

@@ -8,13 +8,6 @@
 Current content object
 ======================
 
-..  versionadded:: 12.4
-    The Extbase-related method
-    :php:`\TYPO3\CMS\Extbase\Configuration\ConfigurationManagerInterface->getContentObject()`
-    was marked as deprecated in TYPO3 v12 and has been removed in TYPO3 v13.
-    Instead, this request attribute can be used to retrieve the current
-    content object.
-
 Instances with :ref:`Extbase controllers <extbase-action-controller>` may need
 to retrieve data from the current content object that initiated the frontend
 Extbase plugin call.

Documentation/ApiOverview/RequestLifeCycle/RequestAttributes/Nonce.rst

@@ -8,8 +8,6 @@
 Nonce
 =====
 
-..  versionadded:: 12.4
-
 The :php:`nonce` request attribute is related to :ref:`content-security-policy`.
 
 ..  seealso::

Documentation/ApiOverview/SessionStorageFramework/UserSessionManagement.rst

@@ -51,11 +51,6 @@ with user sessions. A couple of public methods are available:
 Public API of :php:`UserSession`
 ================================
 
-..  versionchanged:: 12.4.8
-    The signature of the methods :php:`getJwt()` and
-    :php:`resolveIdentifierFromJwt()` has changed. The methods now have an
-    additional argument :php:`$scope`.
-
 The session object created or retrieved by the :php:`UserSessionManager`
 provides the following API methods:
 

Documentation/ApiOverview/SiteHandling/AddLanguages.rst

@@ -139,13 +139,12 @@ Configuration properties
     :type: string
     :Example: :yaml:`en-GB`
 
-    ..  versionchanged:: 12.4
-        The information is now automatically derived from the
-        :ref:`locale <sitehandling-addingLanguages-locale>` setting.
-
     Use this property to override the automatic hreflang tag value for this
     language.
 
+    The information is automatically derived from the
+    :ref:`locale <sitehandling-addingLanguages-locale>` setting.
+
     **Example setups:**
 
     *   You have "German (Germany)" (which is using :yaml:`de-DE` as locale) and

Documentation/ApiOverview/SiteHandling/BaseVariants.rst

@@ -66,14 +66,14 @@ Properties
 ..  option:: typo3.version
 
     :type: string
-    :Example: `12.4.0`
+    :Example: `13.4.0`
 
     The current TYPO3 version.
 
 ..  option:: typo3.branch
 
     :type: string
-    :Example: `12.4`
+    :Example: `13.4`
 
     The current TYPO3 branch.
 
@@ -115,7 +115,7 @@ are available:
 ..  option:: compatVersion
 
     :type: string
-    :Example: `compatVersion("12.4.0")`, `compatVersion("11.5")`
+    :Example: `compatVersion("13.4.0")`, `compatVersion("12.4")`
 
     Match a TYPO3 version.
 

Documentation/Configuration/Typo3ConfVars/BE.rst

@@ -61,33 +61,16 @@ the TYPO3 backend:
     :type: array of file paths
     :Default: :php:`[]`
 
-    ..  versionchanged:: 11.5.35/12.4.11
-        This option has been extended to support an array of root path prefixes to
-        allow for multiple storages to be listed (a string was expected before).
-
-        It is suggested to use the new array-based syntax, which will be applied
-        automatically once this setting is updated via Install Tool configuration
-        wizard. Migration:
-
-        ..  code-block:: php
-            :caption: config/system/settings.php
-
-            // Before
-            $GLOBALS['TYPO3_CONF_VARS']['BE']['lockRootPath'] = '/var/extra-storage';
-
-            // After
-            $GLOBALS['TYPO3_CONF_VARS']['BE']['lockRootPath'] =  [
-                '/var/extra-storage1/',
-                '/var/extra-storage2/',
-            ];
-
-        See also the `security bulletin "Path Traversal in TYPO3 File Abstraction Layer Storages" <https://typo3.org/security/advisory/typo3-core-sa-2024-001>`__.
-
-
     These absolute paths are used to evaluate, if paths outside of the project
     path should be allowed. This restriction also applies for the local driver
     of the :ref:`File Abstraction Layer <fal>`.
 
+    This option supports an array of root path prefixes to
+    allow for multiple storages to be listed.
+
+    See also the `Security bulletin "Path Traversal in TYPO3 File Abstraction
+    Layer Storages" <https://typo3.org/security/advisory/typo3-core-sa-2024-001>`__.
+
     ..  attention::
         Trailing slashes are enforced automatically.
 

Documentation/Configuration/Typo3ConfVars/GFX.rst

@@ -150,7 +150,7 @@ the handling of images and graphics:
     :Path: $GLOBALS['TYPO3_CONF_VARS']['GFX']['processor_stripColorProfileCommand']
     :type: string
 
-    ..  versionchanged:: 11.5.35/12.4.11
+    ..  note::
         This string-based configuration option has been superseded by
         :ref:`$GLOBALS['TYPO3_CONF_VARS']['GFX']['processor_stripColorProfileParameters'] <typo3ConfVars_gfx_processor_stripColorProfileParameters>`
         for `security reasons <https://typo3.org/security/advisory/typo3-core-sa-2024-002>`__.
@@ -183,8 +183,6 @@ the handling of images and graphics:
     :type: array of strings
     :Default: :php:`['+profile', '*']`
 
-    ..  versionchanged:: 11.5.35/12.4.11
-
     Specifies the parameters to strip the profile information, which can reduce
     thumbnail size up to 60KB. Command can differ in IM/GM, IM also knows the
     :bash:`-strip` command. See

Documentation/Configuration/Typo3ConfVars/SYS.rst

@@ -672,8 +672,6 @@ configurations.
         :type: bool
         :Default: false
 
-        ..  versionadded:: 12.4.20
-
         If enabled, the :ref:`Content Security Policy <content-security-policy>`
         is applied in frontend scope as report-only (HTTP header
         `Content-Security-Policy-Report-Only`).
@@ -712,10 +710,6 @@ configurations.
         :type: bool
         :Default: false
 
-        ..  note::
-            This change was introduced as part of the
-            `TYPO3 12.4.4 and 11.5.30 security releases <https://typo3.org/security/advisory/typo3-core-sa-2023-003>`__.
-
         Resolving sites by the `id` and `L` HTTP query parameters is now denied by
         default. However, it is still allowed to resolve a particular page by, for
         example, "example.org" - as long as the page ID `123` is in the scope of the

Documentation/ExtensionArchitecture/FileStructure/ComposerJson.rst

@@ -150,10 +150,6 @@ type
 
 (*required*)
 
-..  versionchanged:: 12.4
-    Extensions in Composer-based installations are installed into the
-    :file:`vendor/` folder.
-
 Use `typo3-cms-extension` for third-party extensions.
 The :file:`Resources/Public/` folder will be symlinked into the
 :ref:`_assets/ <directory-public-assets>` folder of your web root.

Documentation/ExtensionArchitecture/FileStructure/ExtEmconf.rst

@@ -51,7 +51,7 @@ Example:
         'version' => '1.0.0',
         'constraints' => [
             'depends' => [
-                'typo3' => '12.0.0-12.4.99',
+                'typo3' => '13.4.0-12.3.99',
             ],
             'conflicts' => [
             ],
@@ -153,14 +153,14 @@ Example:
          array
    :Description:
          List of requirements, suggestions or conflicts with other extensions
-         or TYPO3 or PHP version. Here's how a typical setup might look:
+         or TYPO3 or PHP version. Here is how a typical setup might look:
 
          .. code-block:: php
             :caption: EXT:some_extension/ext_emconf.php
 
             'constraints' => [
                 'depends' => [
-                    'typo3' => '11.5.0-12.4.99',
+                    'typo3' => '12.4.0-13.4.99',
                     'php' => '7.4.0-8.1.99'
                 ],
                 'conflicts' => [
@@ -186,7 +186,7 @@ Example:
            Loading order especially matters when overriding TCA or SQL of another extension.
 
          The above example indicates that the extension depends on a
-         version of TYPO3 between 11.4 and 12.4 (as only bug and security fixes are
+         version of TYPO3 between 12.4 and 13.4 (as only bug and security fixes are
          integrated into TYPO3 when the last digit of the version changes, it is
          safe to assume it will be compatible with any upcoming version of the
          corresponding branch, thus ``.99``). Also the extension has been

Documentation/ExtensionArchitecture/FileStructure/_ComposerJson/_ExtendedComposer.json

@@ -5,8 +5,8 @@
     "license": "GPL-2.0-or-later",
     "require": {
         "php": "^8.1",
-        "typo3/cms-backend": "^12.4 || ^13.0",
-        "typo3/cms-core": "^12.4 || ^13.0"
+        "typo3/cms-backend": "^12.4 || ^13.4",
+        "typo3/cms-core": "^12.4 || ^13.4"
     },
     "require-dev": {
         "typo3/coding-standards": "^0.7.1"

Documentation/ExtensionArchitecture/HowTo/BackendModule/CreateModule.rst

@@ -24,18 +24,9 @@ is required to return the rendered template:
 
 ..  include:: _ModuleConfiguration/_AdminModuleControllerConstruct.rst.txt
 
-..  versionadded:: 12.1/12.4.9
-    A backend controller can be tagged with the
-    :php:`\TYPO3\CMS\Backend\Attribute\AsController` attribute. This way, the
-    :ref:`registration of the controller <backend-modules-template-without-extbase-manual-tagging>`
-    in the :file:`Configuration/Services.yaml` file is no longer necessary.
-
-    ..  note::
-        Until TYPO3 v12.4.8 the attribute was named
-        :php:`\TYPO3\CMS\Backend\Attribute\Controller` and has been renamed to
-        :php:`AsController` with TYPO3 v12.4.9. Both work with TYPO3 v12 and v13,
-        but developers should use :php:`#[AsController]` for upwards compatibility,
-        since :php:`#[Controller]` has been deprecated with TYPO3 v13.
+..  note::
+    A backend controller should be tagged with the
+    :php:`\TYPO3\CMS\Backend\Attribute\AsController` (:php:`#[AsController]`) attribute.
 
 ..  _backend-modules-template-without-extbase-manual-tagging:
 

Documentation/ExtensionArchitecture/HowTo/BackendModule/CreateModuleWithExtbase.rst

@@ -44,19 +44,9 @@ controller:
         }
    }
 
-..  versionadded:: 12.1/12.4.9
-    A backend controller can be tagged with the
-    :php:`\TYPO3\CMS\Backend\Attribute\AsController` attribute. This way, the
-    :ref:`registration of the controller <backend-modules-template-without-extbase-manual-tagging>`
-    in the :file:`Configuration/Services.yaml` file is no longer necessary.
-
-    ..  note::
-        Until TYPO3 v12.4.8 the attribute was named
-        :php:`\TYPO3\CMS\Backend\Attribute\Controller` and has been renamed to
-        :php:`AsController` with TYPO3 v12.4.9. Both work with TYPO3 v12 and v13,
-        but developers should use :php:`#[AsController]` for upwards compatibility,
-        since :php:`#[Controller]` has been deprecated with TYPO3 v13.
-
+..  note::
+    A backend controller should be tagged with the
+    :php:`\TYPO3\CMS\Backend\Attribute\AsController` (php:`#[AsController]`) attribute.
 
 After that you can add titles, menus and buttons using :php:`ModuleTemplate`: