Is any one else seeing that the new BlockPublicPolicy and RestrictPublicResource settings in Lambda are breaking CloudFormation deployments that create Function URLs?

AWS is rolling out a new feature that blocks public access to Lambda functions by default (https://docs.aws.amazon.com/lambda/latest/dg/permissions-public-access.html) and it just rolled out in eu-west-1 (Ireland). Now any CloudFormation stack I have that creates or updates a Lambda URL fails because this has been turned on by default.