@Kyle well for this particular issue I would have been in trouble if I wasn't randomly browsing the community pages to look what's going on and was going to do the update this night.
I really think as soon as an issue with the latest available build is identified and confirmed, it should immediatly be listed in a "current known issue" sticky thread.
It's true that in some cases the issues can be quickly resolved (custom build, and then in a new release) but even better than resolve the issue is to completly avoid the issue by not updating to the problematic build and waiting for the next one.
Also sometimes the problem are resolved in custom build but can take some time to be released to public through a release. In the meantime, informing your customer about the issues in a dedicated thread would avoid a lot of trouble for your customers that are blindly updating to a build that have new issues.
This could spare us and ST team many time and efforts around known issues.
Kind regards.