I reported this issue to Discourse a few days ago and at the time, they said it might be a caching issue. I haven’t heard back from them about it but I’m sure they’ll get to it after this long weekend.
Not sure, but I’ll get back to you later this week since most of our team’s off on holiday today!
oh, that’s weird its fixed again now. I wonder why it bounced back between versions my cache hadn’t updated and so it loaded the old emoji one again maybe? well whatever xD
I wasn’t sure if you all could tell them to deploy less frequently or something, even though they control the process itself. It sounds like not being updated to the latest version might be a bug on their part.