You’re right, I’m noticing that @miljan and the like may still be unaware.

This exploits a vulnerability in one of our dependencies. Updating the dependency to the latest version fixes the issue. This issue has been fixed and is now live. Let me know if you run into any issues