Looks like there may be an issue with this latest change. We're looking into it.