mirror of
https://github.com/matrix-org/matrix-spec
synced 2026-04-21 10:24:08 +02:00
Compare commits
5 commits
e5c8522e5a
...
6efca8fe36
| Author | SHA1 | Date | |
|---|---|---|---|
|
|
6efca8fe36 | ||
|
|
fb4a0d8f66 | ||
|
|
4c87e0e745 | ||
|
|
92084268f1 | ||
|
|
6ae25e7df4 |
5
.github/workflows/main.yml
vendored
5
.github/workflows/main.yml
vendored
|
|
@ -155,6 +155,11 @@ jobs:
|
||||||
--api server-server \
|
--api server-server \
|
||||||
-r "$RELEASE" \
|
-r "$RELEASE" \
|
||||||
-o spec/server-server-api/api.json
|
-o spec/server-server-api/api.json
|
||||||
|
scripts/dump-openapi.py \
|
||||||
|
--base-url "https://spec.matrix.org${{ needs.calculate-baseurl.outputs.baseURL }}" \
|
||||||
|
--api identity \
|
||||||
|
-r "$RELEASE" \
|
||||||
|
-o spec/identity-service-api/api.json
|
||||||
tar -czf openapi.tar.gz spec
|
tar -czf openapi.tar.gz spec
|
||||||
- name: "📤 Artifact upload"
|
- name: "📤 Artifact upload"
|
||||||
uses: actions/upload-artifact@v4
|
uses: actions/upload-artifact@v4
|
||||||
|
|
|
||||||
|
|
@ -0,0 +1 @@
|
||||||
|
Declare the Application Service Registration schema to follow JSON Schema spec 2020-12.
|
||||||
|
|
@ -0,0 +1 @@
|
||||||
|
The `latest_event` in an aggregated set of thread events uses the same format as the event itself.
|
||||||
1
changelogs/internal/newsfragments/2172.clarification
Normal file
1
changelogs/internal/newsfragments/2172.clarification
Normal file
|
|
@ -0,0 +1 @@
|
||||||
|
GitHub actions are now building the OpenAPI `spec/identity-service-api/api.json` file.
|
||||||
|
|
@ -185,7 +185,7 @@ included under the `m.relations` property in `unsigned` for the thread root. For
|
||||||
```
|
```
|
||||||
|
|
||||||
`latest_event` is the most recent event (topologically to the server) in the thread sent by an
|
`latest_event` is the most recent event (topologically to the server) in the thread sent by an
|
||||||
un-[ignored user](#ignoring-users).
|
un-[ignored user](#ignoring-users). It should be serialized in the same form as the event itself.
|
||||||
|
|
||||||
Note that, as in the example above, child events of the `latest_event` should
|
Note that, as in the example above, child events of the `latest_event` should
|
||||||
themselves be aggregated and included under `m.relations` for that event. The
|
themselves be aggregated and included under `m.relations` for that event. The
|
||||||
|
|
|
||||||
|
|
@ -11,6 +11,7 @@
|
||||||
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
||||||
# See the License for the specific language governing permissions and
|
# See the License for the specific language governing permissions and
|
||||||
# limitations under the License.
|
# limitations under the License.
|
||||||
|
$schema: https://json-schema.org/draft/2020-12/schema
|
||||||
|
|
||||||
type: array
|
type: array
|
||||||
items:
|
items:
|
||||||
|
|
|
||||||
|
|
@ -11,6 +11,7 @@
|
||||||
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
||||||
# See the License for the specific language governing permissions and
|
# See the License for the specific language governing permissions and
|
||||||
# limitations under the License.
|
# limitations under the License.
|
||||||
|
$schema: https://json-schema.org/draft/2020-12/schema
|
||||||
|
|
||||||
type: object
|
type: object
|
||||||
title: Registration
|
title: Registration
|
||||||
|
|
|
||||||
Loading…
Reference in a new issue