@buherator A dot-release 147.0.1 should be available by now, fixing this issue. :)
@buherator no idea. If a big site breaks, we care and try to repair the behavior. Making a new release is not entirely cheap, so a typical fix is to ship a trivial workaround (eg disabling a feature). that gives us time to test and learn more.