Thanks @User - we'll put a proper fix out shortly, but for now please pinning to 3.1.5 looks like it fixes things!