Auto updates has ALWAYS been risky, with any vendor, and OBS Studio is no different. And with Free, Open-Source software, the onus being on end-user to test is assumed (otherwise you'd be paying for a QA team). Further, due to 3rd party plugins, which of course are NOT tested by OBS Studio dev team as part of a release process, if you use ANY plugins, it is up to you to either check with each and every single plugin developer before upgrading, or test yourself. That has been true for last 5 years, and I'd bet since day 1.
And there have been reports for MANY months (this thread being one of them), unrelated to new release about Facebook changing bank-end stream connections (protocol security measures), and their /live/Producer page causing issues
So, a new release not playing well with a moving target... not surprising... other reports indicate others having same issue
However, what the OBS Studio developers would benefit from is more details, as within Facebook there are Scheduled vs Ad-Hoc Events, and there are MANY config options within each of those. And then there is configuring some of that from within OBS Studio on more recent releases, vs configuring yourself within FB's Live/Producer... every single one of those variables can potentially be a separate issue