v0.41.3

The soak's day with a deliberate image change reported the change correctly and then also told the operator that a port had been taken over by the container that had held it all along. It was the one false line left in the 0.41.2 soak's reports, and this release removes it along with its duplicate. It also stops upgrade from replacing a build that is newer than the latest release with that release — the build from make included, which is stamped by git describe — in a fix contributed by @mvanhorn. And it is the first release built by release.yml with the v4 Docker actions, so that 1.0 is not their first run.

🐛 Fixes

• upgrade replaced a binary that was already newer than the latest GitHub release (#307, #312). It treated any version string that was not exactly that release as out of date, so a source build stamped 0.41.1-dev was moved to v0.41.0, and a machine already on a newer tag was moved back while the latest release was still the previous one. A higher MAJOR.MINOR.PATCH is left in place, including one with a suffix, and the line for that machine says it is newer; the summary still counts it as up to date. A make build is stamped by git describe, and v0.41.2-2-gc180322 or v0.41.2-dirty counts as after its tag, so it is left alone too. A real prerelease with the same numbers, such as -rc.1, is still upgraded once that release is out, and a local dev build with no numbers is still refused
• upgrade printed two vs in front of a version that already had one (#313): already vv0.41.2 for every make build exactly at a tag, since git describe stamps the v itself
• report said a port had a new owner when only its container's image had changed (#314). A Docker container owns a port under the label name (image), and the comparison used the whole label, so a container whose image tag moved — or one recreated on a new image — was reported as port: :8082/tcp — it-tools (corentinth/it-tools:latest) → it-tools (8b8128748339), with a needs_attention item saying the port "was not" answered by it at the last report. The image change is already the image line, and a recreated container is replaced. A port now changes hands only when the process or the container's name does. Found on the 0.41.2 soak, the day after an image tag was moved deliberately
• a port reachable on both 0.0.0.0 and [::] that changed hands produced its needs_attention item and its suggested action twice (#314), once per listener. notable_changes already counted it once

📦 Distribution

• the release workflow uses docker/setup-buildx-action and docker/login-action v4 (#301, #302). They were held back because release.yml runs only on a tag, so CI never exercises them; this release is their first run, ahead of 1.0