v1.7.4

Watchdog v1.7.4

Added

• Per-service notification routing with services[].notify.channels, optional severity, and runbook URLs. Services without routing configuration continue to use all globally enabled notification channels.
• Limited, opt-in JSON assertions for HTTP checks through expect.json. Assert exact typed scalar values or regex-match selected string fields using safe property and array-index paths.
• Production Docker distribution with a non-root runtime image, an optional Docker CLI variant, least-privilege Compose configuration, multi-architecture publishing, SBOMs, and provenance metadata.

Improved

• JSON response assertions use the existing bounded private response capture. Response bodies and asserted values are never written to logs, state, metrics, history, or the status page.
• Docker containers now forward stop signals through active Watchdog check processes and preserve Watchdog’s documented exit code during graceful shutdown.

Fixed

• Long-running container checks no longer end with Docker’s forced-kill exit code when stopped; Watchdog cleanup completes and returns the expected runtime result.