The previous update 2.0.38 (that introduced this bug on MacOS 10 and 11) was 5 days ago, not last night. Today (20 hours ago) hotfix 2.0.38 was released to address the specific issue.
Please checkout the Early Access > Software Release Notes and look at the post’s timestamp.
Summary
If you’re running MacOS 10 or 11 the hotfix should be installed as it fixes the identified issue, if on a later MacOS it is optional (as there was no issue) thus there is no benefit, equally there is no harm. either. (Caveat, any software change carries a degree of risk.)
Time to move on, for me at least, and enjoy the music.