Carries everything from beta.41/42 plus two fixes found this week.
Queued updates no longer wait for the right thread. Tapping a container while something else is updating queues it — but that queue was only worked off at the end of a Telegram single update, while the lock is taken in eleven places. An entry queued while the scheduled run, the Web UI or a self-update held it waited for the next Telegram update to happen to end. On my own instance that was a day. Nothing was lost; it just sat there. The poll loop picks it up now.
already in the queue says since when, instead of reading like "you already pressed this" to someone pressing a button for the first time. And /status lists what is queued, which was reported nowhere at all.
A release tag that disagrees with app/version.py now fails the build. v2.18.0 was tagged on a commit whose version file still read 2.18.0-beta.35, so :latest has been reporting itself as a beta ever since — noticed from the outside by @famewolf, who never left the stable channel. The code there is the released code; the name on it is wrong. The next stable puts the name right.
Beta.41/42 notes still apply: v2.18.0-beta.42.
Worth testing: queue three updates at once and see that all three run, and whether /status shows what is waiting.