TYPO3-Documentation · linawolf · Feb 6, 2026 · Feb 6, 2026
diff --git a/Documentation/Concepts/Extensions/Index.rst b/Documentation/Concepts/Extensions/Index.rst
@@ -37,7 +37,7 @@ the following data:
         "name": "myvendor/my-extension",
         "type": "typo3-cms-extension",
         "require": {
-            "typo3/cms-core": "^13.4",
+            "typo3/cms-core": "^14",
         },
         "extra": {
             "typo3/cms": {

diff --git a/Documentation/Concepts/TypoScript/Index.rst b/Documentation/Concepts/TypoScript/Index.rst
@@ -24,12 +24,6 @@ and with their properties and functions in the
 "Hello world" example in TypoScript
 ===================================
 
-..  versionchanged:: 13.1
-    The site set can be used as
-    :ref:`TypoScript provider <t3coreapi:site-sets-typoscript>`. It is not
-    necessary to use a TypoScript record as is explained in tutorials for
-    TYPO3 versions 12.4 and below.
-
 Put the following TypoScript in a file called :file:`setup.typoscript` within
 your :ref:`Site set <t3coreapi:site-sets>`. The site set is the folder
 containing your :ref:`site configuration <site-configuration>`.

diff --git a/Documentation/FirstProject/Settings.rst b/Documentation/FirstProject/Settings.rst
@@ -83,10 +83,6 @@ Find detailed information in :ref:`TYPO3 Explained, Site handling <t3coreapi:sit
 Site settings
 -------------
 
-..  versionadded:: 13.3
-    Starting with TYPO3 v13.3, site settings can also be edited in the site
-    settings editor.
-
 You can edit site settings in the :guilabel:`Sites > Setup > Settings` module.
 Changes are written to the :file:`config/sites/my-site/settings.yaml` file. If you
 keep this file under version control, you must commit and push the changes made

diff --git a/Documentation/FirstProject/SiteManagement/Index.rst b/Documentation/FirstProject/SiteManagement/Index.rst
@@ -50,9 +50,6 @@ The site identifier can be arbitrary, so we use "example_site" here. The
 entry point should be a URL pointing to the web root. In this example, it is
 a local URL generated by `DDEV <https://ddev.com/>`__.
 
-..  versionadded:: 13.1
-    Site sets have been added with TYPO3
-
 From the list of available sets, choose the set for your site package if you
 have one. You can learn how to create a site package in the
 :ref:`TYPO3 Sitepackage Tutorial <t3sitepackage:start>`.
@@ -103,8 +100,6 @@ Site management: Trouble shooting
         If the site package is installed but the site package set is still not
         available the set or one of its dependencies might be corrupted.
 
-        ..  versionadded:: 13.4.5
-
         ..  figure:: /FirstProject/SiteManagement/InvalidSiteSet.png
             :alt: Screenshot of the "Site Configuration" module with an invalid site set displayed
 

diff --git a/Documentation/Installation/Setup.rst b/Documentation/Installation/Setup.rst
@@ -18,10 +18,6 @@ Install Tool.
 Set up TYPO3 using the console
 ===============================
 
-..  versionadded:: 12.1
-    Starting with TYPO3 12.1, a new CLI command `typo3 setup` is available
-    as an alternative to the traditional web-based installer.
-
 To perform an interactive guided setup, run:
 
 ..  code-block:: bash

diff --git a/Documentation/Installation/Updates/Index.rst b/Documentation/Installation/Updates/Index.rst
@@ -57,8 +57,8 @@ Major, minor and patch level updates
 In TYPO3 you can update your TYPO3 version. There exist three different types
 of updates:
 
-#.  Major updates: for example, from 12.4.23 to 13.0.0
-#.  Minor updates: for example, from 13.0 to 13.1
+#.  Major updates: for example, from 13.4.23 to 14.0.0
+#.  Minor updates: for example, from 14.0 to 14.1
 #.  Patch and bugfix level updates (often security updates): for example, from 13.4.0 to 13.4.1
 
 
@@ -87,9 +87,9 @@ In TYPO3, we can separate a TYPO3 update into three stages: the :ref:`pre-upgrad
 Minor updates
 -------------
 
-Minor changes - `11.*.2`: For example 11.5 has new functionalities compared to
-11.4. The version 11.5 is compatible with 11. So within a version like major
-11, the steps do not lead to breaking changes. For example in version 13.3
+Minor changes - `13.*.2`: For example 13.4 has new functionalities compared to
+13.3. The version 13.4 is compatible with 13. So within a version like major
+13, the steps do not lead to breaking changes. For example in version 13.3
 compared to version 13.2 a new
 :ref:`Feature: #101252 - Introduce ErrorHandler for 403 errors with redirect option <changelog:feature-101252-1715447531>`
 was introduced.
@@ -101,7 +101,7 @@ Usually minor and patch changes are also referred to as **non-breaking** changes
 Patchlevel updates
 ------------------
 
-Patchlevel changes - `11.5.*`: The version 11.5.2 indicates a backwards-compatible bugfix or patch release.
+Patchlevel changes - `13.4.*`: The version 13.4.2 indicates a backwards-compatible bugfix or patch release.
 It can be for example a security update. Clear the cache and check if the website is working as expected. For
 further information we refer to the :ref:`Patch/Bugfix update guide<t3coreapi:minor>`.