Thanks for the report! This has been fixed internally.
Looks like it just didn’t make it into the patch. I’ve made a note of this.