It's a bug! I've verified and fixed it locally, but we haven't released the fix yet.
Will get back to you with an ETA!
