Skip to content

Pulse

v5.1.33 Feature

This release adds 2 notable features for engineering teams evaluating rollout.

Published 5d 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
+12 more
self-hosted host-monitoring infrastructure-monitoring kubernetes monitoring proxmox proxmox-backup-server proxmox-mail-gateway proxmox-ve react typescript webhooks

Affected surfaces

rbac

Summary

AI summary

Updates Validation Summary, v5.1.33, and Safety across a mixed release.

Changes in this release

Feature Medium

Adds opt-in RBAC enforcement for Pulse Pro via Settings > Access Control.

Adds opt-in RBAC enforcement for Pulse Pro via Settings > Access Control.

Source: llm_adapter@2026-05-29

Confidence: high

Feature Low

Records direct guest-agent memory value in diagnostic snapshots for debugging.

Records direct guest-agent memory value in diagnostic snapshots for debugging.

Source: llm_adapter@2026-05-29

Confidence: high

Bugfix Medium

Fixes Proxmox guest memory selection using MemAvailable fallback for saturated Linux memory reports.

Fixes Proxmox guest memory selection using MemAvailable fallback for saturated Linux memory reports.

Source: llm_adapter@2026-05-29

Confidence: high

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-05-29 11:46:52 UTC
Workflow: Pulse Release Pipeline #259

Validation Summary

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

v5.1.33

Fixes

  • Added opt-in RBAC enforcement for Pulse Pro on v5.1.x. Roles can now be enforced from Settings > Access Control when an active Pro license includes RBAC.
  • Fixed Proxmox guest memory selection for QEMU guest-agent payloads that report saturated Linux memory, using MemAvailable fallback where appropriate.
  • Recorded the direct guest-agent memory value in diagnostic snapshots to make future memory-source debugging clearer.

Safety

  • RBAC enforcement stays disabled by default so existing installations keep their current access behavior until an administrator enables it.
  • RBAC enforcement can be disabled with PULSE_RBAC_ENFORCEMENT=false and a restart if recovery is needed.

Installation

If you run Pulse via Docker or Compose, update to rcourtman/pulse:5.1.33.

See the Installation Guide for other deployment methods.

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 →

Beta — feedback welcome: [email protected]