-
Notifications
You must be signed in to change notification settings - Fork 4.7k
[Release gate]: Matrix live homeserver smoke check before v0.8.0 stable #6576
Copy link
Copy link
Closed
Labels
channelAuto scope: src/channels/** changed.Auto scope: src/channels/** changed.channel:matrixAuto module: channel/matrix changed.Auto module: channel/matrix changed.enhancementNew feature or requestNew feature or requestpriority:p2Medium priorityMedium priorityrelease-gateRelease gate findingRelease gate findingrisk: lowAuto risk: docs/chore-only paths.Auto risk: docs/chore-only paths.status:acceptedRFC or work item accepted and ratified by the team.RFC or work item accepted and ratified by the team.status:no-staleExempt from the 60-day stale auto-close policy.Exempt from the 60-day stale auto-close policy.
Milestone
Metadata
Metadata
Assignees
Labels
channelAuto scope: src/channels/** changed.Auto scope: src/channels/** changed.channel:matrixAuto module: channel/matrix changed.Auto module: channel/matrix changed.enhancementNew feature or requestNew feature or requestpriority:p2Medium priorityMedium priorityrelease-gateRelease gate findingRelease gate findingrisk: lowAuto risk: docs/chore-only paths.Auto risk: docs/chore-only paths.status:acceptedRFC or work item accepted and ratified by the team.RFC or work item accepted and ratified by the team.status:no-staleExempt from the 60-day stale auto-close policy.Exempt from the 60-day stale auto-close policy.
Type
Fields
Give feedbackNo fields configured for issues without a type.
Projects
StatusShow more project fields
Backlog
Summary
Add a v0.7.6 release-gate smoke check for Matrix channel behavior after the matrix-sdk 0.17 bump landed in #6566.
Problem statement
#6566 merged the matrix-sdk 0.16 -> 0.17 compatibility bump plus the
channel-matrixrecursion-limit fix and low-memory install heuristic. The PR was reviewed and merged with green CI, but both the PR body and reviews explicitly noted that no live Matrix homeserver smoke test was run.That is acceptable for merging the dependency/compile fix, but before shipping a release that includes the bump, we should verify the main runtime Matrix flows against a real homeserver so SDK API compatibility is not only compile/test-suite confidence.
Proposed solution
Before v0.7.6 ships, run a live Matrix smoke test on a real homeserver covering:
Record the tested commit/version, homeserver type if relevant, and any known skips. If one of these paths fails, open or link a follow-up bug and decide whether it blocks the release.
Non-goals / out of scope
Acceptance criteria
Architecture impact
Matrix channel runtime validation only. No code architecture change is proposed by this issue.
Risk and rollback
Low implementation risk: this is a release validation task. The risk being managed is shipping matrix-sdk 0.17 without a real-homeserver sanity check.
Breaking change?
No
Data hygiene checks