mirror of
https://github.com/matrix-org/matrix-spec
synced 2025-12-24 09:58:38 +01:00
36b02edfc2
Fixes #3305 Fixes #3380 The idea here is to better distinguish between a 'raw' event (as we send over the wire), and the 'serialised' format, as sent in responses to the C-S api and in `PUT /_matrix/app/v1/transactions/{txnId}`. It's made more complicated by the fact that there are _two_ serialisation formats, one used by `/sync` and `/notifications`, and one by everything else (the difference being whether `room_id` is included). In an ideal world, we wouldn't repeat `SerialisedEvent` every time it's used, and instead just link to the first reference, but that's a job for another day. Another job for another day is to get rid of things like `sync_state_event.yaml` (which is now used only in one place, so should be inlined.) |
||
|---|---|---|
| .. | ||
| appendices/newsfragments | ||
| application_service/newsfragments | ||
| client_server/newsfragments | ||
| identity_service/newsfragments | ||
| legacy | ||
| push_gateway/newsfragments | ||
| room_versions/newsfragments | ||
| server_server/newsfragments | ||
| header.md | ||
| pyproject.toml | ||
| README.md | ||
Changelogs
Towncrier is used to manage the changelog and keep it up to date. Because of this, updating a changelog is really easy.
Generating the changelog
Please see the release docs for more information.
Creating a new changelog
There are a few places you'll have to update:
/layouts/shortcodes/changelog/changelog-changes.htmlto account for the new changelog./scripts/generate-changelog.shto render the changelog for releases.- Supporting documentation such as the contributing guidelines.