-
-
Notifications
You must be signed in to change notification settings - Fork 9.6k
Remove Gitter Notifier / add Matrix Notifier #52862
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.
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
Comments
Thank you for this suggestion. |
yes. At least for the Symfony codebase, we should remove the Gitter Notifier if the Gitter API is no longer available. |
See #57658 |
This PR was merged into the 7.2 branch. Discussion ---------- [Notifier] Remove the Gitter bridge | Q | A | ------------- | --- | Branch? | 7.2 | Bug fix? | no | New feature? | yes <!-- please update src/**/CHANGELOG.md files --> | Deprecations? | no <!-- please update UPGRADE-*.md and src/**/CHANGELOG.md files --> | Issues | Fix #52862 <!-- prefix each issue number with "Fix #", no need to create an issue if none exists, explain below instead --> | License | MIT The Gitter API does not exist anymore. Commits ------- e0a1a90 [Notifier] Remove the Gitter bridge
Any plans to implement matrix? |
But to be honest it would only work with Matrix Synapse or other server implementations that also implement the server-client api v3. So older Matrix Synapse server or server that doesn't implement the server-client api v3 won't be covered by this. I only tested it with a Matrix Synapse Docker Image v1.90.0 |
Symfony version(s) affected
>=5.3.0
Description
The Gitter API is no longer available, and was slated for removal as far back as January 2023 (https://blog.gitter.im/2023/01/16/gitter-is-going-fully-native-matrix-in-feb-2023/), with removal taking place in February 2023 (https://blog.gitter.im/2023/02/13/gitter-has-fully-migrated-to-matrix/).
What can be done
Since this API is no longer supported, Symfony should:
(and optionally)
How to reproduce
Attempt to use the Gitter Notifier component.
Possible Solution
see list item # 2 above
Additional Context
No response
The text was updated successfully, but these errors were encountered: