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.

1.0.0

The first release of WUD Queue, an integration that installs What's Up Docker's container updates one at a time. Pressing several install buttons at once, or Home Assistant's own "Update all", makes WUD run the installs side by side, its own update among them, and compose files written in the same second can end up with the wrong versions. The queue puts the installs in a line, WUD's own container last, and stops at the first failure.

It pairs with WUD Queue card, released alongside it, which shows the queue and fills it with a button. The integration works through its actions alone too.

Also in this release

• The queue is sensor.wud_queue. Its state is idle, running, stopped or failed, and its attributes list the items in order with their versions and status, so every dashboard shows the same queue.
• Four actions run it. wud_queue.enqueue adds updates, stop lets the current item finish and leaves the rest, retry picks up after a failure, and clear puts a finished queue away. A finished queue also clears itself after ten minutes.
• Services of one compose project that run the same image and are headed for the same version are one item. A stop waits for the whole item, so a compose file is never left with only some of its services updated.
• WUD reports no failures, so the queue works them out. An install fails when Home Assistant refuses to send it, when WUD doesn't start it within a minute, when the container is still on its old version two minutes after WUD finished, or when it runs for half an hour.
• wud_queue_failed and wud_queue_finished events let an automation send a notification or keep a log.
• An install counts as done once the container reaches its new version, even when WUD leaves its own entity marked as installing after replacing itself. A container that WUD is recreating is waited out while its entity is briefly unavailable.
• Texts in English and Finnish.