✅ 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-11 15:37:18 UTC
Workflow: Pulse Release Pipeline #153
Validation Summary
- All required assets present ✓
- Checksums verified ✓
- Version strings correct ✓
- Binary architectures validated ✓
Final 5.1 stabilization release
This wraps up the 5.1 stabilization series. Critical and security fixes will continue as needed, but the bulk of development focus is now on the next major version, which has been in the works for a while and I'm very excited about. Thanks for your patience with the frequent updates over the past week.
Fixes
- Agent auto-update restart — The agent would download new binaries but silently fail to restart, leaving the old version running. Users had to manually reinstall after every server upgrade. The agent now exits on restart failure so the service manager picks up the new binary automatically. (#1247)
- Metrics database bloat — The metrics database could grow to 5GB+ because deleted data was never reclaimed. Now runs a one-time vacuum on upgrade to reclaim disk space, with incremental vacuum on every cleanup going forward. First startup after upgrading may take a few extra seconds while the database is compacted. (#1231)
- Storage mixing across instances — Shared storage with the same name on different Proxmox instances was incorrectly merged into a single entry. (#1246)
- Backup attribution on shared storage — When standalone PVE hosts share NFS storage and have overlapping VMIDs, backups could be randomly attributed to the wrong guest. Now detects the ambiguity and skips rather than guessing. (#1177, #1251)
- Disk temperature fallback — Some drives don't populate the top-level SMART temperature field. Now falls back to ATA attributes 194/190. (#1243)
- SSO/SAML routes — SSO provider management and SAML login flow endpoints (login, ACS, metadata, logout, SLO) were not registered, causing 404s for all SSO configuration and SAML authentication.
Installation
Docker (recommended):
docker pull rcourtman/pulse:5.1.9Docker Compose:
Update your docker-compose.yml to use rcourtman/pulse:5.1.9
See the Installation Guide for complete setup instructions.