Skip to content

Pulse

v6.0.3 Bugfix

This release fixes issues for SREs watching stability and regressions.

Published 21d Monitoring & Metrics
✓ No known CVEs patched
Read the diff → Tool health → What is this tool? →

✓ No known CVEs patched in this version

Topics

ai alerts web docker docker-monitoring go
+13 more
self-hosted infrastructure-monitoring kubernetes monitoring proxmox proxmox-backup-server proxmox-mail-gateway proxmox-ve solidjs truenas typescript vsphere webhooks

Affected surfaces

breaking_upgrade auth

Summary

AI summary

Updates Validation Summary, Promotion Metadata, and ✅ Release Asset Validation across a mixed release.

Full changelog

✅ Release Asset Validation (Post-Publish): PASSED

Assets were revalidated after publication due to a release edit.

Status: Live release assets re-validated ✅
Validated: 2026-07-05 11:32:33 UTC
Workflow: Pulse Release Pipeline #286

Validation Summary

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

Pulse v6.0.3 Release Notes

v6.0.3 is a stable patch release for the Pulse v6 line. It follows
v6.0.2 and focuses on the remaining v5-to-v6 agent upgrade failure reported
after the first two v6 patch releases.

Fixes

  • Fixed v5 agent update recovery when the generated update command supplies an
    explicit Pulse URL but the old running v5 agent process is still the only
    source for the token and enabled telemetry scopes. The installer now merges
    the explicit URL with the recovered process state instead of failing with
    "No existing Pulse Agent connection state found."
  • Treated incomplete saved v6 agent state as recoverable during --update.
    This keeps the update path on the legacy recovery branch whenever any
    required connection detail is still missing.
  • Allowed carrier-grade NAT / overlay network addresses in 100.64.0.0/10 as
    local-network HTTP and WebSocket targets for Pulse agent connections. This
    fixes deployments that legitimately use addresses such as
    http://100.100.100.5:7655 while keeping public non-local addresses on the
    HTTPS-required path.
  • Refreshed Docker, Helm, and installer release metadata for the stable patch
    line.

Upgrade Notes

Use the normal v6 install or update flow for v6.0.3. The rollback target for
this patch release is v6.0.2.

If a v5.1.35 agent upgrade failed on v6.0.0, v6.0.1, or v6.0.2, rerun the
current update command from Settings -> Infrastructure after updating the
Pulse server to v6.0.3.

Installation

Docker (recommended):

docker pull rcourtman/pulse:6.0.3

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

See the Installation Guide for complete setup instructions.

Paid Pulse Pro, Relay, and eligible legacy customers: public GitHub release assets and the public rcourtman/pulse Docker image are community builds. They do not include the private Pulse Pro runtime hooks. Use https://pulserelay.pro/download.html with your activation key to get the private Pulse Pro Docker image or Linux/LXC archive.

Promotion Metadata

  • Promotion channel: stable
  • Candidate stable tag: v6.0.3
  • Promoted prerelease tag: n/a
  • Rollback target: v6.0.2
  • Rollback command: ./scripts/install.sh --version v6.0.2
  • Hotfix exception: true
  • Hotfix reason: Fix confirmed v5.1.35 to v6 agent upgrade failures still reported after v6.0.2.

Weekly OSS security release digest.

The CVE patches and breaking changes that affected production tools this week. One email, every Sunday.

No spam, unsubscribe anytime.

Share this release

Track Pulse

Get notified when new releases ship.

Sign up free

About Pulse

Real-time monitoring for Proxmox, Docker, and Kubernetes with AI-powered insights, smart alerts, and a beautiful unified dashboard

All releases →

Related context

Beta — feedback welcome: [email protected]