v2.2.1

What's new in v2.2.1

Two bugs that end-to-end testing found and the unit suite could not: a
kill that could never stop a Docker container, and a force kill that only
worked from the list. The README now describes the app that exists.

Fixed

• portnanny kill could not stop a Docker container. It scanned
  without asking for container names, so it never had one, and every
  Docker-published port answered "a container docker ps can name" and
  stopped nothing, while portnanny whois on the same port printed the
  exact docker stop command it would not run. The MCP kill_port had it
  too. A kill now fetches the name when a target is a container it cannot
  name yet, and pays the docker ps only then.
• Command-Return force killed a selected row but not a typed one. With
  kill 3000 in the search field it sent a plain SIGTERM, contradicting
  the keyboard help and the code's own comment.

Changed

• The README was checked line by line against the code and rewritten
  around what it found: eighteen claims were wrong or misleading, among
  them Command-K killing "the current filter" (on All it kills dev
  servers), "hide UDP sockets" (the switch shows them, and is on),
  "the only network request" (the inspector's peek is a local one), and
  a scan taking "about 20 ms with no subprocesses" (kernel calls in a few
  milliseconds, with lsof and ps as fallbacks). It also documents the
  right-click menu and that the Tests filter lists test processes rather
  than ports, neither of which it mentioned before.
• Tests/e2e/ holds the harness that caught the Docker bug: the guard and
  the MCP server driven against real listeners. Manual, not in CI, since
  it needs real processes and Docker.

---

📦 Install

Download PortNanny-2.2.1.dmg below, open it, and drag PortNanny to
Applications. Universal binary: runs natively on Apple Silicon and Intel;
requires macOS 13 (Ventura) or newer.

Not notarized (no Apple Developer account). First launch on macOS 15 or
newer: open it once, then System Settings → Privacy & Security → Open
Anyway. On macOS 13 and 14: right-click PortNanny.app → Open → Open.
Either way, xattr -dr com.apple.quarantine /Applications/PortNanny.app
skips the dialog. Homebrew (brew install --cask portnanny) does this for you.

What's Changed

• README says what the app does, and says it once by @mukes555 in #55
• portnanny kill can stop a Docker container again by @mukes555 in #56
• Keep the end-to-end harness that caught the Docker bug by @mukes555 in #57
• Release 2.2.1 by @mukes555 in #58

Full Changelog: v2.2.0...v2.2.1