1.0.1

A fix release for the queue's edge cases. The most visible one: on a night when What's Up Docker had an update for itself, the queue could fail right after WUD had updated fine, because the container WUD leaves behind when it replaces itself was queued along with it.

What to do after upgrading

Nothing. The queue, its sensor, actions and events work as before, and automations that queue updates keep working, the README's nightly example included.

Also in this release

• The container WUD leaves behind when it updates itself is no longer queued. It has WUD's image and project, so it joined WUD's own item and was then installed in vain.
• A container that is already being installed, for example from Home Assistant's own update dialog, is left out of the queue. Before, Home Assistant refused its install and the whole run failed there, leaving the rest of the updates out.
• A container whose entity is unavailable or gone when its turn comes is waited for, up to five minutes, before its install is sent. Home Assistant drops an install for such an entity without a word, so the queue used to wait half an hour for an install that was never sent.
• A retry puts WUD's own container last again, as it should go after everything else.
• A stop asked for while the last item installs ends the run as idle rather than stopped, as nothing was left out.
• When nothing could be queued, the message says it may be because the containers are already queued, already being installed or up to date.
• The README follows the order of the other integrations', and the repository has its issue templates and funding file.