v1.16.0
Adds a reference page for two upgrade failures that present as application bugs: an engine upgrade that cuts socket-reading sidecars off from the Docker API, and an image upgrade refused on a compatibility claim nobody measured.
Engine and image upgrades
references/engine-and-image-upgrades.md is new, written by @CybotTM in #81.
The Docker API floor moves inside a major series, in both directions. Engine 29.0.0 requires API 1.44; 29.3.0 lowers it again to 1.40. A container negotiating below the running floor is refused, and the refusal presents as an empty container list rather than an error — the proxy serves an empty routing table and every host answers 404. Anything reading /var/run/docker.sock carries a pinned client version, so one engine upgrade breaks reverse proxies, log shippers, autoheal and monitoring sidecars at once, each in its own domain language. The page carries the per-release table with the release-note quotes, the docker version reads for the server floor and the local client, a curl probe against the socket for a chosen API version, and the rule that a proxy reporting no routers while the containers are up and labelled is an API-version problem until its log is read.
Verify an image upgrade with a probe container. Release notes describe what changed, not what your configuration uses, so the page gives the rehearsal instead: the candidate on the same network, alternate ports, the production configuration with routing untouched and only the outward side effects overridden — ACME CA at the staging directory, certificate store on a throwaway path, discovery namespace and metrics name isolated — each edit made in a copy that is diffed against the original. The probe script asserts the routing outcome and exits non-zero on an unexpected status, since curl exits 0 on any HTTP response.
Both halves are measured rather than reasoned: the engine upgrade took a live shop to 404 until its proxy was replaced, and the assumption that a new proxy major would reject the existing router labels was wrong — a probe on the production network settled it in one run.
Maintenance
Pre-commit hook netresearch/skill-repo-skill updated to v2.1.0 (#79) and v2.1.1 (#80).
Full Changelog: v1.15.2...v1.16.0