This is actually really bad.

It breaks people’s perfectly-legit native SQL queries with postgres typecasts.

I wonder if there’s any way to roll this change back without breaking.

Well, I it looks like it’s a completely undocumented “feature”, so I guess it’s probably OK to just call it a bug and fix it.