Thanks everyone!
I have identified the broken plugins as the ones responsible for sending Discourse push notifications to iphones (where the standard Discourse way doesn’t work), namely @featheredtoast’s GitHub - featheredtoast/discourse-pushover-notifications: Pushover notifications for Discourse · GitHub as well as my GitHub - Sprachprofi/discourse-fcm-notifications: Send Discourse push notifications through FCM to any custom app · GitHub . The Ember code is identical in both of them and very simple, just a couple extra fields in the admin and one extra field in the user profile, with checks on whether push notifications are already active or not. Given that the retirement of the EMBER_VERSION switch means I cannot see any deprecation warnings or error messages that might help me narrow down which of those few lines is a problem, I asked Github Copilot for advice on what might have changed between Ember 3 and Ember 5 and I’m trying those suggestions. If you have ideas, I’m all ears.
Let me just reiterate that this is not how a breaking change should be pushed and I am deeply disappointed with Discourse. Several policies that go against all wisdom:
- putting non-technical people on the tests-passed rather than LTS version by default
- compounding this by not even mentioning the possibility of putting oneself on a more stable version in the official installation guide; it is only known to forum insiders who presumably have less need of it
- making reversion to an earlier, working version impossible
- compounding this by also guaranteeing the backward compatibility of the project is less than two months, through deliberate removal of the EMBER_VERSION flag. Other projects have backward compatibility of a year, and those are projects where it’s also possible to revert to older versions.