v0.4.0

Added

• Mark rows and delete them together. In Images, Volumes and Networks, Space marks
  a row and a every row the filter shows; d then deletes all marked rows, skipping
  any in use, and Esc clears the marks.
• Clean up volumes in one go. D deletes every dangling, orphaned or unused volume
  among the rows shown, listing how many of each there are and the space they take before
  you pick.
• Abandoned anonymous volumes are marked. One that no container mounts reads
  ○ dangling instead of ○ unused: with no name to ask for it by, nothing will mount
  it again.

v0.3.3

Changed

• s asks how far to go. Stop stays on y; d and v in the same dialog remove the
  container or take the stack down, keeping or deleting its volumes. A running container
  is stopped gracefully before it is removed.

Added

• Act on a whole compose stack. On a stack header or over its detail, s, S, r
  and k stop, start, restart or kill every service — dependencies start first and stop
  last, as compose does.
• Take a stack down. d removes its containers and networks like
  docker compose down, and v deletes its volumes too, as down -v does. Networks and
  volumes another container still uses are kept.
• Remove a container with its anonymous volumes. v in the remove dialog runs
  docker rm -v; named volumes are never deleted.

v0.3.2

Added

• Every list filters as you type. / now works in all five views, not just Stacks,
  and narrows the list with each key; Enter keeps the filter so the view's keys act on
  the matches, and Esc clears it.
• Filters look past the name. Containers and services also match on image, ID and
  compose project; images on their ID and every tag, not just the one listed; volumes and
  networks on driver and project.

v0.3.1

Fixed

• A port published on all interfaces was listed twice — since 0.1.0. Docker reports
  it on both 0.0.0.0 and ::; dockza now shows it once, and sorts ports so they stop
  reshuffling between polls.
• An image pulled by digest showed a mangled name — since 0.1.0. Docker's containerd
  image store lists it as repo@sha256:…, which read as repository repo@sha256; it now
  splits at the @.

Changed

• Enter on a stack opens its detail instead of expanding or collapsing it — → /
  ← still do that.

Added

• Images, networks and stacks get a detail panel. Enter opens one: an image's tags
  and the containers created from it; a network's subnets, gateways and attached
  containers, with their addresses and DNS names; a stack's compose files, services,
  volumes and networks.
• A container's detail shows what it connects to: its image and stack, published
  ports with a URL for each, its address and DNS names on each network, and the
  containers it relates to through depends_on, --network container: or
  --volumes-from, both ways round.
• Every reference is a link. Enter on any of those rows opens the image, stack,
  network, volume or container it names, and [ comes back.
• Lists say who uses what. The Images and Networks lists gain a USED BY column,
  replacing the Networks list's container count, and the NET, PORTS and TAG columns add
  +N where there is more than the one shown.
• Containers running an outdated image are marked. An orange ↑ flags a container
  whose image tag now points at a newer local image, where the list used to show a bare
  image ID; the image's detail says superseded by <tag>.
• Leftovers of removed compose projects are marked. A volume or network whose
  project has no containers left reads ○ orphaned.
• An anonymous volume's detail names the image that created it, from the VOLUME
  a container mounts it at — so only while one does.
• Enter in the log viewer opens the container's detail; [ returns to the logs.
• More to copy. y adds a port's URL or -p spec, a container's address and DNS
  names on a network, an image's tags, a network's subnets and gateways, and a stack's
  compose files and working directory.

v0.3.0

Fixed

• Mount sources were blank or pointed inside Docker Desktop's VM — since 0.1.0. An
  anonymous volume showed no source and a bind read /host_mnt/…; MOUNTS now names each
  volume and shows a bind's host path.

Added

• See which containers use a volume. The Volumes list gains a USED BY column, and
  Enter opens a volume's detail: its mountpoint, where it came from (a compose project,
  or anonymous), and every container mounting it, running or stopped.
• Follow a mount to its volume, and a volume to its containers. Tab moves the
  cursor between a detail panel's sections, and Enter on a mount or a USED BY row opens
  the volume or container it names.
• Back and forward through the screens you visited. [ and ] (or Alt+← /
  Alt+→) step through them, followed links included, returning to the row and section
  the cursor was on.
• More to copy from a detail panel. y copies from the selected row, or with none
  selected from the panel's subject: a container's name, ID or image; a mount's source,
  destination or docker run -v spec; a volume's name or mountpoint.

v0.2.6

Fixed

• Keys typed while help was open acted on the view behind it — since 0.1.0. S
  started the selected container, x opened a shell, d raised a hidden "Remove
  container?" confirm, and Esc closed the detail panel instead of the help. Help now
  holds the keyboard until it closes.
• The footer fell back to list hints over an open detail panel or log viewer — since
  0.1.0. Every poll re-sent the list selection, replacing the panel's key hints within
  seconds; they now stay until the panel closes.

Added

• Environment variables can be browsed and read in full. e used to list them with
  values cut at 55 characters; now ↑/↓ select a variable and Enter expands it to
  its full value, multi-line ones included (E expands all).
• Copy environment variables to the clipboard. y in the detail panel copies the
  selected variable's name, value or NAME=value, or all of them. It uses the
  platform's clipboard tool, or over SSH an OSC 52 escape to the terminal — see the
  README's Clipboard section.

v0.2.5

Fixed

• The selected row was all but invisible. Its indigo highlight snapped to near-black
  #1c1c1c under blessed's 256-colour matching, barely a shade off the background — in
  every list view, and since 0.1.0. Lists now highlight on an indigo that survives the
  match.

Changed

• Services now sit indented under their stack. Every service row started in the stack
  name's own column, leaving the elbow as the only cue that it was nested. Service rows
  now step three columns right — ├─ on each, └─ on the last — taking the width out of
  the image column.

v0.2.4

Fixed

• Top-bar counters ran into their status dots. The running and errored counts in
  the top right rendered as ●7 and ●1, with no gap between the coloured dot and
  the number. Both now carry a space, matching the stopped counter, which has no dot.

v0.2.3

Changed

• Node.js 24 is now the minimum. engines.node moves from >=20 to >=24, and
  CI drops its Node 20 and 22 legs — the matrix is now Node 24 across Ubuntu, macOS
  and Windows. Nothing in the source requires 24 specifically; the bump aligns the
  supported range with what CI actually exercises, so behaviour on 20 and 22 is no
  longer verified rather than known to be broken. npm warns instead of refusing on an
  engine mismatch, so existing installs on older Node keep running untested.
  @types/node moves 20.x → 24.x to match, and the README requirement is updated.

v0.2.2

Fixed

• Deleted rows came back. Removing an image (and likewise a volume or network)
  made the row vanish and then reappear a few hundred milliseconds later, even
  though Docker had really deleted it; it stayed on screen until the next poll.
  A background poll issued before the deletion landed after it and wrote its
  pre-delete snapshot over the fresh list. The same race hit container actions on
  the Containers and Stacks views, where a stopped container would flip back to
  running for a few seconds. Listings are now owned solely by the polling loop
  and carry a generation token, so a response a mutation has outraced is discarded
  instead of applied.
• Side-rail and top-bar counters desynced from the list after any action. The
  rail could report N images while the list showed N-1, and stopping a container
  from the Stacks view recomputed the top-bar running/stopped/errored counts from
  a stale container array — producing numbers that were wrong, not merely late.
  A mutation now refreshes the list, both container views and every counter together.
• Resizing the terminal could undo a container action. The Containers list was
  repainted on resize from a cache the action never updated, so a removed container
  reappeared when the window changed size.