Add /_matrix/versions to spec
This commit is contained in:
parent
ae7a1f2e6c
commit
5e30d75ccb
3 changed files with 54 additions and 0 deletions
|
@ -106,6 +106,8 @@ Some API endpoints may allow or require the use of ``POST`` requests without a
|
|||
transaction ID. Where this is optional, the use of a ``PUT`` request is strongly
|
||||
recommended.
|
||||
|
||||
{{versions_http_api}}
|
||||
|
||||
Client Authentication
|
||||
---------------------
|
||||
Most API endpoints require the user to identify themselves by presenting
|
||||
|
|
|
@ -36,3 +36,14 @@ Before we formally started releasing the specification, the last working copy
|
|||
we had can be found `here`__.
|
||||
|
||||
.. __: https://matrix.org/docs/spec/legacy/
|
||||
|
||||
Versioning
|
||||
----------
|
||||
|
||||
The specifications are each versioned in the form ``rX.Y.Z``.
|
||||
|
||||
Changes to ``X`` and ``Y`` should not be assumed to be compatible with any other version.
|
||||
|
||||
For a fixed ``X`` and ``Y``, any ``Z`` should be assumed to be compatible with any lesser ``Z``.
|
||||
|
||||
For example, it is safe to assume that a server which claims to implement ``r0.1.2`` supports ``r0.1.0``, but not vice-versa.
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue