Remove `<compatibility>` documentation from package.xml page

see #298

diff --git a/docs/package/package-xml.md b/docs/package/package-xml.md
index c26811cb22711a2974f63329d11c8b7d49adf518..2199e9be0a4229575c57a809868027604b55b959 100644 (file)
--- a/docs/package/package-xml.md
+++ b/docs/package/package-xml.md
@@ -129,27 +129,6 @@ Example:
 
 The attribute `version` must be a valid version number as described in the [\<version\>](#version) section. In the example above it will be impossible to install this package in WoltLab Suite Core 6.0.0 Alpha 1 or higher.
 
-### `<compatibility>`
-!!! info "Available since WoltLab Suite 3.1"
-!!! warning "With the release of WoltLab Suite 5.2 the API versions were abolished. Instead of using API versions packages should exclude version `6.0.0 Alpha 1` of `com.woltlab.wcf` going forward."
-
-WoltLab Suite 3.1 introduced a new versioning system that focused around the API compatibility and is intended to replace the `<excludedpackage>` instruction for the Core for most plugins.
-
-The `<compatibility>`-tag holds a list of compatible API versions, and while only a single version is available at the time of writing, future versions will add more versions with backwards-compatibility in mind.
-
-Example:
-
-```xml
-<compatibility>
-       <api version="2018" />
-</compatibility>
-```
-
-#### Existing API versions
-
-| WoltLab Suite Core | API-Version | Backwards-Compatible to API-Version |
-|---|---|---|
-| 3.1 | 2018 | n/a |
 
 ### `<instructions>`