monitoring

Update docker.io/rcourtman/pulse Docker tag to v5.1.14

Michi Kofler-Häusler

25 Feb 2026 — 1 min read

No problems upgrading the Docker container with a Docker compose yaml file by means of Watchtower DevOps resp. GitOps with dependency update facilitated by Mend's Renovate Bot.
Including updating all docker and host agents manually.

This MR contains the following updates:

Package	Update	Change
docker.io/rcourtman/pulse	patch	`5.1.13` → `5.1.14`

Release Notes

rcourtman/Pulse (docker.io/rcourtman/pulse)

`v5.1.14`: Pulse v5.1.14

Compare Source

✅ Release Asset Validation (Post-Publish): PASSED

Assets were revalidated after publication due to a release edit.

Status: Live release assets re-validated ✅
Validated: 2026-02-25 00:14:37 UTC
Workflow: Pulse Release Pipeline #165

Validation Summary

All required assets present ✓
Checksums verified ✓
Version strings correct ✓
Binary architectures validated ✓

What's Changed

Bug Fixes

fix(notifications): resolved webhook notifications now sent to all webhook services (#1259) — Recovery/resolved alerts were only sent via email; webhooks (Telegram, Discord, Slack, Teams, PagerDuty, etc.) silently rejected the payload because it used the firing template format. Now uses service-specific resolved templates with proper formatting for each service.
fix(docker): batch container updates no longer fail with 400 (#1289) — "Update All" button fired parallel requests but the backend only allows one command per host at a time. Now serializes updates within each host while still parallelizing across different hosts.
fix(notifications): use service-specific templates for resolved webhooks (#1068) — Related foundation work for the resolved webhook fix above.
fix(docker): stop CPU bars flickering for idle containers (#1288) — CPU usage bars no longer disappear and reappear on the dashboard for idle containers.
fix(patrol): cap per-run tokens and reset patrol session history — Prevents unbounded token usage in AI patrol runs.

New Features

feat(alerts): add dedicated backup-orphaned alert type (#1286) — Orphaned backups now trigger their own alert type for better detection and notification.

Other

fix(ai): deduplicate Docker host 3-way chain in mention picker (#1252)

Installation

Docker (recommended):

docker pull rcourtman/pulse:5.1.14

Docker Compose:
Update your docker-compose.yml to use rcourtman/pulse:5.1.14

See the Installation Guide for complete setup instructions.

Update docker.io/sonarqube Docker tag to v26.3.0.120487

Major upgrade to Docker container executed successfully by means of Watchtower infrastructure with dependency update facilitated by Mend's Renovate Bot. This MR contains the following updates: Package Update Change docker.io/sonarqube minor 26.2.0.119303-community → 26.3.0.120487-community

Update docker.io/matomo Docker tag to v5.8.0

No problems automatically updating the Docker image, migrating the application manually and run the container by Watchtower with dependency update facilitated by Mend's Renovate Bot. This MR contains the following updates: Package Update Change docker.io/matomo minor 5.7.1 → 5.8.0 Release Notes matomo-org/matomo

Update ghcr.io/paperless-ngx/paperless-ngx Docker tag to v2.20.10

No problems upgrading the Docker container with a Docker compose yaml file within Portainer and by means of Portainer DevOps resp. GitOps with dependency update facilitated by Mend's Renovate Bot. This MR contains the following updates: Package Update Change ghcr.io/paperless-ngx/paperless-ngx patch 2.20.9 → 2.

Update docker.io/hashicorp/vault Docker tag to v1.21.4

No problems upgrading the Hashicorp Vault Docker container with a Docker compose yaml file within Portainer and by means of Portainer DevOps resp. GitOps with dependency update facilitated by Mend's Renovate Bot. This MR contains the following updates: Package Update Change docker.io/hashicorp/vault patch 1.21.