github getwud/wud 9.2.0

6 hours ago
  • 🚀 [CLI] Add one-shot headless mode (WUD_RUN_MODE=oneshot): run wud watch as a single scan with JSON output on stdout, exit codes for CI, --fail-on-update, --update-available, --format=ndjson, and version/--help commands. No database is created. See One-Shot Headless Mode.
  • 🚀 [WATCHER] Add container name regex exclusion filter for Docker watcher (fixes #897, fixes #985)
  • 🚀 [REGISTRY] Add custom User-Agent to registry requests (fixes #685)
  • 🐛 [WATCHER] Fix container temporary name persistence when containers are renamed (fixes #770)
  • 🚀 [PROMETHEUS] Add option to disable authentication for metrics endpoint (#878)
  • 🚀 [UI] Display dedicated provider icons for triggers matching documentation
  • 🚀 [API/UI] Add Server-Sent Events (SSE) support and asynchronous container watch
  • 🐛 [TAG] Harden tag candidate filtering and SemVer comparison against exotic variants and pre-releases (fixes #1278)
  • 🐛 [REGISTRY] Fix HTTPS proxy support for outgoing requests (fixes #982)
  • 🐛 [TRIGGER] Gracefully handle missing watcher in Docker and Docker Compose triggers (fixes #1287)
  • 📚 [DOCS] Comprehensive guide for remote Docker hosts and multi-host monitoring (fixes #579)
  • 🚀 [TRIGGER] Add Pre and Post Update Hooks support for Docker and Docker Compose triggers
  • 🚀 [WATCHER] Report the remote version label and build date of a digest update: result.version (from org.opencontainers.image.version) and result.created are now resolved from the remote image config, so the API, Prometheus and triggers can describe a digest update as 2.3.6 -> 2.3.7 instead of sha256:8978d2f5 -> sha256:3eb277ac. Each remote digest is resolved at most once and reused while the update stays pending, and the config digest already known from the manifest is reused where possible, so an up-to-date container costs no extra registry request and a pending one costs a single blob fetch

Don't miss a new wud release

NewReleases is sending notifications on new releases.