Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Drop unstable MSC4151 after November 19th, 2024 #17373

Closed
turt2live opened this issue Jun 28, 2024 · 1 comment · Fixed by #18052
Closed

Drop unstable MSC4151 after November 19th, 2024 #17373

turt2live opened this issue Jun 28, 2024 · 1 comment · Fixed by #18052
Assignees
@turt2live

Comments

@turt2live
Copy link
Member

This will be plenty of time for clients to switch to stable endpoints.

Search code for this issue URL for details.
@turt2live turt2live self-assigned this Jun 28, 2024
@turt2live turt2live mentioned this issue Jun 28, 2024
Merged
@turt2live
Copy link
Member Author

the date in this issue is a lie. I've removed it until a date can actually be established.

@turt2live turt2live changed the title Drop UnstableReportRoomRestServlet after 2-3 releases (~August 13th, 2024) Drop UnstableReportRoomRestServlet after 2-3 releases Aug 7, 2024
@turt2live turt2live changed the title Drop UnstableReportRoomRestServlet after 2-3 releases Drop UnstableReportRoomRestServlet after 2-3 releases (TBD when) Aug 7, 2024
anoadragon453 added a commit that referenced this issue Oct 31, 2024
@turt2live @anoadragon453
Support & use stable endpoints for MSC4151 (#17374)
c705bee 
matrix-org/matrix-spec-proposals#4151 has
finished FCP.

See #17373 for unstable
endpoint removal

---------

Co-authored-by: Andrew Morgan <andrew@amorgan.xyz>
@turt2live turt2live changed the title Drop UnstableReportRoomRestServlet after 2-3 releases (TBD when) Drop unstable MSC4151 after November 19th, 2024 Nov 4, 2024
turt2live added a commit that referenced this issue Dec 26, 2024
@turt2live
Drop unstable MSC4151 implementation
bab5c32 
It's been rotated out of known clients, and should be safe for removal now.

Fixes #17373
@turt2live turt2live mentioned this issue Dec 26, 2024
Merged
3 tasks
turt2live added a commit that referenced this issue Jan 7, 2025
@turt2live
Drop unstable MSC4151 implementation (#18052)
beea39f 
It's been rotated out of known clients, and should be safe for removal
now.

Fixes #17373

### Pull Request Checklist

<!-- Please read
https://element-hq.github.io/synapse/latest/development/contributing_guide.html
before submitting your pull request -->

* [x] Pull request is based on the develop branch
* [x] Pull request includes a [changelog
file](https://element-hq.github.io/synapse/latest/development/contributing_guide.html#changelog).
The entry should:
- Be a short description of your change which makes sense to users.
"Fixed a bug that prevented receiving messages from other servers."
instead of "Moved X method from `EventStore` to `EventWorkerStore`.".
  - Use markdown where necessary, mostly for `code blocks`.
  - End with either a period (.) or an exclamation mark (!).
  - Start with a capital letter.
- Feel free to credit yourself, by adding a sentence "Contributed by
@github_username." or "Contributed by [Your Name]." to the end of the
entry.
* [x] [Code
style](https://element-hq.github.io/synapse/latest/code_style.html) is
correct
(run the
[linters](https://element-hq.github.io/synapse/latest/development/contributing_guide.html#run-the-linters))
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@turt2live turt2live

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Drop unstable MSC4151 implementation element-hq/synapse
1 participant
@turt2live