✅ Release Asset Validation (Post-Publish): PASSED
Assets were revalidated after publication due to a release edit.
Status: Live release assets re-validated ✅
Validated: 2026-03-25 15:08:40 UTC
Workflow: Validate Release Assets #80
Validation Summary
- All required assets present ✓
- Checksums verified ✓
- Version strings correct ✓
- Binary architectures validated ✓
This is a short v5 release candidate focused on user-reported maintenance fixes. It is intended to get validation on current bug reports before the next stable v5 release.
Fixed
- Recovery notifications: preserves queued resolved notifications correctly when alerts clear, and keeps quiet-hours handling intact.
- NAS/alerting fixes: improves false RAID degraded suppression for QNAP and Synology-style system arrays, fixes alert counts in resource stats, and corrects threshold-driven alert coloring/override handling.
- Backup and storage fixes: resolves template backup orphan false positives and shared-storage override matching.
- Proxmox fixes: hardens setup-script token extraction and SSH key handling, accepts API token aliases used by external clients, and improves Proxmox auto-registration recovery when registrations go stale.
- Agent/update fixes: allows missing host-agent binaries to be proxied from GitHub releases for update/download paths.
- Docker fixes: preserves custom URLs across recreated containers, respects active filters for Update All, and clears stale update alerts correctly when update notifications are disabled.
- AI fixes: preserves provider metadata in model lists, respects configured Patrol provider/model selection, restarts chat services correctly after provider/model changes, and handles empty/null chat-session payloads safely.
- Reporting/UI fixes: resolves report generation against the correct org metrics store, keeps saved full-width layout preference applied after auth, and fixes the PBS settings table full-width layout.
- Metrics/monitoring fixes: reduces metrics-store write churn, scopes Proxmox cluster TLS fingerprints correctly, makes VM memory carry-forward more conservative, and keeps alert-side node display names instance-aware.
RC testing
If you reported one of the related issues, please test v5.1.25-rc.1 specifically and report back whether the issue is resolved.
Installation
If you run Pulse via Docker or Compose, update to rcourtman/pulse:5.1.25-rc.1.
See the Installation Guide for other deployment methods.