-
-
Notifications
You must be signed in to change notification settings - Fork 9.6k
[Notifier] Bump conflict rules for all notifier bridges #39559
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
Conversation
derrabus
commented
Dec 18, 2020
Q | A |
---|---|
Branch? | 5.x |
Bug fix? | no |
New feature? | no |
Deprecations? | no |
Tickets | N/A |
License | MIT |
Doc PR | N/A |
What about removing all of them actually? |
We have already released version 5.2.0 of the bridges that claim compatibility with Notifier 5.3. |
I don't like them either, but imho we should not remove them before 6.0. Otherwise, we would allow Composer to make a bad decision. |
Then shouldn't we specifically conflit with the only bridges that have a 5.2.0 tag? |
be6fea7
to
fed253b
Compare
All of the bridges listed here existed in 5.2 already. Note that for some of the bridges, the 5.1.0, 5.1.1 and 5.1.2 tags are also affected. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm really sad we have to maintain such a boilerplate...
I agree. 😞 |