Releases · Dozzle

Dozzle adds host metrics, log filters, and updates with a rollback

Two releases in three days: 11.2.0 puts load, disk and uptime on the host card and adds a time filter for logs; 11.3.0 turns container updates into a managed operation that can roll back.

By BoneThursday 8 October 20262 min readReleases

entryread only

filedThursday 8 October 2026

length2 min

sectionReleases

subjectDozzle

sourceson the page

Previously — Monday 28 September 2026Dozzle v11.1.2 hardens the log viewer's edges: escaping, sanitizing, scoping

Dozzle shipped two releases in three days, and together they move the log viewer from watching containers to carefully touching them. Version 11.3.0 is the one to read: updates become a managed feature, with safe updates that can roll back, automatic update modes, reliable update records, and reporting into the project’s optional cloud layer. A dedicated setting governs container updates, and the fix list shows the feature getting its edges sanded the same week, from reliable rollbacks to trimming leftover code from the 11.2 series. For a tool whose job is answering what just happened, owning the update operation is a coherent next step: the change and its record happen where you are already looking.

The rest of 11.3.0

Container disk usage gets real: each container shows its writable-layer size, Docker volume sizes fold into the disk column, and the host card gains reclaimable space. A fleet-wide image update check shares one pass across containers, settings split into proper pages, and a handful of fixes land, including Fail2ban log levels, a one-time state on the cloud link callback, and error memory only reading printed lines. The settings reorganization deserves its own mention: setup steps now live on their own pages instead of one long scroll.

What 11.2.0 brought

The previous release, three days earlier, put the machine itself on the host card: load with color coding against the core count, disk usage, uptime, and extra drives, which is the class of numbers you otherwise ssh in for. Logs got a time-range filter, so what happened between the restart and the first request is a filter rather than a scroll. Kubernetes mode learned about rollout restarts and newer images, and the mobile interface was rebuilt with a native-feeling shell and a floating tab bar. The quieter half was a fix list organized around state honesty: a container that died stops being shown as live everywhere, and a reconnecting event stream keeps your open views instead of dropping them. The remaining entries are the small courtesies: the update action hides itself where it cannot work, the update flow recreates containers that share a network with the updated one, login screens stay out of browser history, and Swarm update checks skip exited tasks.

My read

A log viewer earns trust by never presenting yesterday as live, and both of these releases keep polishing exactly that surface, with 11.3 extending the honesty to mutating operations: updates with records and a rollback instead of a hope and a restart. The changelog credit line still names the maintainer and his model collaborator side by side, the tool stays entirely local, and the managed layer stays optional. If you self-host Dozzle, both updates are no-thought installs.

Source: the v11.3.0 release, following v11.2.0.

SecurityDozzle v11.1.2 hardens the log viewer's edges: escaping, sanitizing, scopingA small release for the self-hosted Docker log viewer where most of the fixes share one theme: untrusted text — container names, log lines, image labels — now gets escaped or sanitized everywhere it could reach beyond plain display.

ReleasesHomebridge 2.5.0 is a Matter release: new device types, and fixes for identity and cacheHomebridge 2.5.0 adds Matter device types for solar, battery, EV chargers, meters, tariffs and water heaters, and spends the rest of its list on behaviour that used to go wrong: air quality reporting only two levels, thermostats registering late, restored accessories losing their uniqueId or owner, and cache reads that took the accessory with them. It also bumps @matter/main to v0.18.0 and @homebridge/hap-nodejs to v2.3.0.

ReleasesMealie 3.30.0 lets you own the AI prompt, time each step, and plan a whole weekMealie 3.30.0 moves AI prompt control into the app, so prompts can be appended to, replaced or extended with global instructions, and it retires the OPENAI_CUSTOM_PROMPT_DIR variable while importing existing prompts automatically. Instruction steps gain individual durations, meal plan entries can cover a full week, and a batch of fixes tightens import scoping, locale lookup and the permissions needed to manage units, tools, labels and recipe actions.