Thanks for the report. This is now addressed.
Just a note that we’ve been working on an automated plugin compatibility notification system for a while now and we’ll be releasing it along with some big custom-wizard updates in the new year.
The system picked up this compatibility issue an hour after the relevant commit went into discourse/discourse, and pushed a warning to the plugin clients, which you would have seen in your admin dashboard before you upgraded (screenshot is from our test instance; this functionality is not yet released).
