We initially thought we had a fix, but upon further investigation, we discovered a deeper issue. I agree, we could have been better at updating the bug with this information.
In the meantime, the severity of the issue became more obvious, which is why we accelerated the fix and deployed it today (May 5th) ahead of the regular weekly push scheduled for tomorrow (May 6th).
In the meantime, the severity of the issue became more obvious, which is why we accelerated the fix and deployed it today (May 5th) ahead of the regular weekly push scheduled for tomorrow (May 6th).