I'm pretty busy and this is a convenience thing in my view, and not looking to me like a high priority at the moment. I see the need, but I'm in triage mode at the moment with my time. Very busy.
But... this is one of the reasons the stable channel builds exist. You could switch to that, and then you'll only get notices when a new build in stable is offered, which historically is just a few times a year. You can install latest for anything bleeding-edge that you need if that comes up, and go back to stable again later.
The other factor in this is that I don't want people lingering on old builds. That's a support nightmare for me. So much so that if you report a bug to me on any version that isn't current in the channel you are using, I'm going to reflexively ask you to update to the most recent release in the channel and try again. In some cases, I may even ask you to try latest.
Also, while I try to keep the release notes pretty accurate and in sync with the changes to the code, I do miss things from time to time, particularly when I'm in a hurry, so some fixes don't get mentioned by error of omission. Some are intentionally screened out (e.g. I can clean up some messy or poorly-structured code I see, and that would not even warrant a mention in the release notes, but the act of replacing or refactoring the code may fix a bug that I wasn't even aware was there -- and yes, there's always a risk of an injection when I do this as well, but I do spend a lot of time testing).
Anyway, my recommendation at this point is to just switch to stable if you need immediate relief. The current stable build is 23242, and is built from the latest 23242 code base (so its release notes apply). The stable builds are always done this way.
