mirror of
https://github.com/matrix-org/matrix-spec
synced 2026-02-23 14:33:43 +01:00
Compare commits
1 commit
6efca8fe36
...
e5c8522e5a
| Author | SHA1 | Date | |
|---|---|---|---|
|
|
e5c8522e5a |
5
.github/workflows/main.yml
vendored
5
.github/workflows/main.yml
vendored
|
|
@ -155,11 +155,6 @@ jobs:
|
|||
--api server-server \
|
||||
-r "$RELEASE" \
|
||||
-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
|
||||
- name: "📤 Artifact upload"
|
||||
uses: actions/upload-artifact@v4
|
||||
|
|
|
|||
|
|
@ -1 +0,0 @@
|
|||
The `latest_event` in an aggregated set of thread events uses the same format as the event itself.
|
||||
|
|
@ -1 +0,0 @@
|
|||
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
|
||||
un-[ignored user](#ignoring-users). It should be serialized in the same form as the event itself.
|
||||
un-[ignored user](#ignoring-users).
|
||||
|
||||
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
|
||||
|
|
|
|||
Loading…
Reference in a new issue