fix(federation): Name the cause when invite state uses stripped events #2111

Closed
mmaudet wants to merge 3 commits from mmaudet/continuwuity:fix/invite-legacy-stripped-state-error into main

3 commits

Author SHA1 Message Date
cd7cfc8faf
chore: Add changelog news fragment
Some checks failed
Checks / Changelog / Check changelog is added (pull_request_target) Successful in 7s
Documentation / Build and Deploy Documentation (pull_request) Has been cancelled
Checks / Prek / Pre-commit & Formatting (pull_request) Has been cancelled
Checks / Prek / Check changed files (pull_request) Has been cancelled
Checks / Prek / Clippy and Cargo Tests (pull_request) Has been cancelled
2026-08-07 08:07:48 +02:00
445400c540
docs: Explain why federated invites are rejected with M_INVALID_PARAM
Two duplicate reports of this were filed within three days of each other.
2026-08-07 07:24:04 +02:00
864f848e82
fix(federation): Name the cause when invite state uses stripped events
An invite whose invite_room_state still uses pre-v1.16 stripped state was
rejected as though the entry were a malformed PDU, and the only diagnosis
was a debug-level log line. Distinguish the two cases: say that the entry
is a stripped state event and that Matrix 1.16 requires full PDUs, and log
the rejection at warn level with the origin server.
2026-08-07 07:24:04 +02:00