Skip to content

armgit / Pulse

Public Imported from GitHub
0

Real-time monitoring dashboard for Proxmox VE, PBS, Docker, Kubernetes, TrueNAS and vSphere. Self-hosted, with alerts for failed backups, full disks, unhealthy containers and offline nodes.

Prepare v6.7.0-beta.3

pulse-triage[bot]d8402d1da91e
diff --git a/VERSION b/VERSION
index bb49ab89b7..d9ea631b1c 100644
--- a/VERSION
+++ b/VERSION
@@ -1 +1 @@
-6.7.0-beta.2
+6.7.0-beta.3
diff --git a/deploy/helm/pulse/Chart.yaml b/deploy/helm/pulse/Chart.yaml
index 9d6cb09f2d..47d4b8255f 100644
--- a/deploy/helm/pulse/Chart.yaml
+++ b/deploy/helm/pulse/Chart.yaml
@@ -2,9 +2,9 @@ apiVersion: v2
name: pulse
description: Helm chart for deploying the Pulse hub and optional Docker, Kubernetes, or OpenShift monitoring agent.
type: application
-version: 6.7.0-beta.2
-appVersion: "6.7.0-beta.2"
-icon: https://raw.githubusercontent.com/rcourtman/Pulse/v6.7.0-beta.2/docs/images/pulse-logo.svg
+version: 6.7.0-beta.3
+appVersion: "6.7.0-beta.3"
+icon: https://raw.githubusercontent.com/rcourtman/Pulse/v6.7.0-beta.3/docs/images/pulse-logo.svg
keywords:
- monitoring
- proxmox
@@ -32,7 +32,7 @@ annotations:
description: Smoke tests with kind cluster deployment
artifacthub.io/links: |
- name: Documentation
- url: https://github.com/rcourtman/Pulse/blob/v6.7.0-beta.2/docs/KUBERNETES.md
+ url: https://github.com/rcourtman/Pulse/blob/v6.7.0-beta.3/docs/KUBERNETES.md
- name: Support
url: https://github.com/rcourtman/Pulse/discussions
artifacthub.io/maintainers: |
diff --git a/deploy/helm/pulse/README.md b/deploy/helm/pulse/README.md
index afc855bb70..9987ee93c9 100644
--- a/deploy/helm/pulse/README.md
+++ b/deploy/helm/pulse/README.md
@@ -1,6 +1,6 @@
# pulse
-![Version: 6.7.0-beta.2](https://img.shields.io/badge/Version-6.7.0--beta.2-informational?style=flat-square) ![Type: application](https://img.shields.io/badge/Type-application-informational?style=flat-square) ![AppVersion: 6.7.0-beta.2](https://img.shields.io/badge/AppVersion-6.7.0--beta.2-informational?style=flat-square)
+![Version: 6.7.0-beta.3](https://img.shields.io/badge/Version-6.7.0--beta.3-informational?style=flat-square) ![Type: application](https://img.shields.io/badge/Type-application-informational?style=flat-square) ![AppVersion: 6.7.0-beta.3](https://img.shields.io/badge/AppVersion-6.7.0--beta.3-informational?style=flat-square)
Helm chart for deploying the Pulse hub and optional Docker, Kubernetes, or OpenShift monitoring agent.
diff --git a/docker-compose.yml b/docker-compose.yml
index a735f41933..48afc7ac47 100644
--- a/docker-compose.yml
+++ b/docker-compose.yml
@@ -2,7 +2,7 @@ version: '3.8'
services:
pulse:
- image: ${PULSE_IMAGE:-rcourtman/pulse:6.7.0-beta.2}
+ image: ${PULSE_IMAGE:-rcourtman/pulse:6.7.0-beta.3}
container_name: pulse
restart: unless-stopped
logging:
diff --git a/docs/RELEASE_NOTES.md b/docs/RELEASE_NOTES.md
index bc3759d474..90fc694a69 100644
--- a/docs/RELEASE_NOTES.md
+++ b/docs/RELEASE_NOTES.md
@@ -7,8 +7,8 @@ For historical v4 notes that previously lived in this repo, see:
`docs/releases/RELEASE_NOTES_v4.md`
For the current v6 beta packet, see:
-- `docs/releases/RELEASE_NOTES_v6.7.0-beta.2.md`
-- `docs/releases/V6_CHANGELOG_v6.7.0-beta.2.md`
+- `docs/releases/RELEASE_NOTES_v6.7.0-beta.3.md`
+- `docs/releases/V6_CHANGELOG_v6.7.0-beta.3.md`
For the current stable v6 packet, see:
- `docs/releases/RELEASE_NOTES_v6.6.0.md`
diff --git a/docs/UPGRADE_v6.md b/docs/UPGRADE_v6.md
index fe5b746960..ca6c789731 100644
--- a/docs/UPGRADE_v6.md
+++ b/docs/UPGRADE_v6.md
@@ -9,8 +9,8 @@ public Community downloads do not replace a private Pro build.
For the current v6 beta packet, see:
-- `docs/releases/RELEASE_NOTES_v6.7.0-beta.2.md`
-- `docs/releases/V6_CHANGELOG_v6.7.0-beta.2.md`
+- `docs/releases/RELEASE_NOTES_v6.7.0-beta.3.md`
+- `docs/releases/V6_CHANGELOG_v6.7.0-beta.3.md`
For the current stable v6 packet, see:
diff --git a/docs/releases/RELEASE_NOTES_v6.7.0-beta.3.md b/docs/releases/RELEASE_NOTES_v6.7.0-beta.3.md
new file mode 100644
index 0000000000..77cf0f0470
--- /dev/null
+++ b/docs/releases/RELEASE_NOTES_v6.7.0-beta.3.md
@@ -0,0 +1,145 @@
+# Pulse v6.7.0-beta.3 Release Notes
+
+This beta follows `v6.7.0-beta.2` on the way to stable `v6.7.0`. Stable `v6.6.0` remains the rollback target.
+
+Pulse v6.7.0 makes backup status clearer when reads fail, dates are uncertain or tasks disagree. It also strengthens configuration recovery, reduces chart processing, restores TrueNAS CORE readings, and improves disk visibility, agent updates and SSO settings.
+
+## Highlights
+
+- Proxmox Backups now counts completed restore points separately from running and failed entries.
+- TrueNAS CORE monitoring now loads CPU and memory readings previously blocked by rejected reporting requests.
+- Settings Recovery now rejects incomplete configuration backups before they can replace existing settings.
+
+## What's improved
+
+- **Charts use less server work.** Workload history needs less decoding, copying and temporary memory. Proxmox live updates also create fewer temporary objects.
+- **History stays still while browsing.** Drawer charts reserve space for changing values and times, keeping controls steady under the pointer. Peak labels stay beside the plotted spike.
+- **Expanded lists scroll correctly.** Platform and backup tables account for expanded details, keeping lower rows reachable without unexpected gaps or jumps.
+- **Backup browsing survives refreshes.** Open Backups views update inventory, readings and badge colours while preserving the selected view, filters, expanded details and chart focus.
+- **Retry keeps keyboard focus.** Backups preserves a usable focus position through failed reads, retries and recovery, including when an error message disappears.
+- **Tables work better with keyboards.** Platform headings have focusable sort buttons that respond to Enter and Space.
+- **Rows and details stay readable.** Machines, workloads, Infrastructure, thresholds and platform tables keep status cues and actions compact. Detail tables adapt to their available panel width.
+- **Controls remain reachable.** Settings actions stay visible, deep drawers scroll properly, and Infrastructure and Patrol actions have clearer accessible names. Agent Doctor commands support keyboard scrolling.
+- **Dark text has clearer contrast.** Muted labels are easier to read in dark mode.
+- **What's New is easier to scan.** After an update, changes appear as plain lists with warnings first, without hidden groups.
+
+## Alerts and notifications
+
+- **Alert History avoids repeated names.** Rows show the condition beside the resource rather than naming it again. Compact actions leave more room for descriptions.
+- **Deleted destinations stay deleted.** Webhook removal confirms success in the editor. Queued deliveries cannot borrow another destination's permission because it shares the same URL.
+- **Audit webhook drafts survive errors.** Rejected entries remain available for correction, and a completed save does not erase a newer draft.
+- **Delivery activity supports keyboard browsing.** The notification log can be focused and scrolled, and refreshes preserve keyboard position.
+- **PBS timing restarts after missing readings.** Gaps in CPU or memory data interrupt activation and recovery timing without clearing existing warnings.
+- **Docker alert controls show their actual scope.** Thresholds removes ineffective runtime switches. Guidance explains that Offline Alerts covers runtime connectivity, while containers need their own settings.
+- **Recovery rules are easier to understand.** Troubleshooting explains why falling usage can leave an alert open, including clear thresholds, recovery delays, averaged readings and missing observations.
+
+## Disks and storage
+
+- **Real container data disks remain visible.** Filesystem monitoring includes real mounts under /var/lib/docker and /var/lib/containers while continuing to exclude container layers.
+- **Missing disk readings stay unknown.** Host charts and History no longer record unavailable filesystem usage as zero or substitute an unmeasured live value.
+- **Disk warnings need recovery evidence.** Missing agent filesystems or unavailable Proxmox node readings cannot clear alerts or advance confirmation timing. Linked hosts retain the established alert owner to prevent duplicates.
+- **Storage warnings require usable capacity.** Usage thresholds and forecasts ignore missing or contradictory capacity readings. Explicitly disabling the warning still takes effect.
+- **macOS lists exclude hidden mounts.** Time Machine and other hidden system mounts no longer appear as ordinary disks by default. Explicit disk includes remain available.
+- **Local backup copies stay independent.** Identical paths on separate PVE nodes remain separate copies. Reads, failures, disabled storage and running files stay scoped to the correct local disk.
+- **Archives stay with the right guest type.** PVE uses archive paths rather than storage names to identify VM and LXC backups. Reused VMIDs and explicitly unknown archive types cannot give the wrong guest protection credit.
+- **Missing-filesystem help avoids storage changes.** Guidance distinguishes real data disks from excluded layers and remote mounts, without asking users to move data or change backup selection.
+
+## Proxmox, PBS and backups
+
+- **Incomplete reads preserve inventory.** Failed or malformed PVE snapshot and storage listings cannot erase retained entries. PBS preserves unread namespaces when siblings succeed, while respecting explicit access refusals.
+- **Old evidence cannot become fresh again.** Retained PVE snapshots and cached PBS backups from failed reads no longer renew protection evidence. Recognised older guest identities still match Coverage.
+- **Failed assessments withdraw outdated claims.** Coverage rejects failed, malformed or inconsistent assessment responses and offers Retry. Large inventories use complete batches, and leaving the view cancels outstanding reads.
+- **Uncertain evidence remains inspectable.** Coverage keeps restore details available when assessments fail. Partial history shows Attention where appropriate, provider scope is identified, and empty details distinguish current from retained evidence.
+- **Dates must describe a real instant.** Backup ages, Workloads completion labels and assessments reject malformed or ambiguous dates. Future backup or verification dates remain uncertain and explain which clocks to check.
+- **Ended jobs stop looking active.** Completed jobs clear running-backup indicators. Missing guest results stay Unknown, and unread cached logs cannot keep renewing activity.
+- **Activity follows inventory filters.** Search, node, type, source, location and verification filters narrow the chart. Selecting a day narrows only the list, and calendar dates remain correct across clock changes.
+- **Unknown backup sizes remain visible.** Volume charts mark days containing completed points with unavailable sizes. Bars show known volume, so missing sizes no longer look like zero activity.
+- **Prune retention cannot hide verification.** Backups kept during pruning still show Verified or Unverified. Retention appears separately, and unavailable verification is labelled Not reported.
+- **Task failures have inspectable details.** Expanded Coverage rows show status, start time, duration, error, task ID and reported origin. Missing, future or tied start times expose possible latest tasks instead of choosing an OK result.
+- **Backup sources and guest placement stay distinct.** Restore evidence names its reading connection and supports searching it. Workloads retain their owning PVE identity, while repository names cannot become guest node names.
+- **Location filters keep their boundaries.** Similar repositories on different connections stay separate. Ambiguous saved filters request a new selection. Notices explain that filtered ages and evidence do not recalculate workload-wide protection.
+
+## TrueNAS, vSphere and Docker
+
+- **History finds the correct source.** TrueNAS and vSphere resource drawers preserve the provider's history identity when loading through the resource API.
+- **TrueNAS dates reflect completed work.** Collection time no longer becomes snapshot creation time, including older stored records. Start times and running replication timestamps cannot appear as completed work.
+- **Undated replication problems stay visible.** Failed, warning and running states remain visible without invented dates. A reported success without a known run time stays Unknown.
+- **Failed protection refreshes are visible.** TrueNAS Protection warns when displaying retained events and offers Refresh. Its guide explains snapshot, replication and collection limits.
+- **Docker updates wait for health checks.** Pulse waits up to three minutes for replacement containers' initial checks and detects restarting containers. Verification remains inconclusive while health is still starting.
+
+## Install, updates and agents
+
+- **Docker setup preserves existing deployments.** The helper stops when a Compose configuration already exists, protecting custom ports, mounts, image pins and credentials. It distinguishes prepared configuration from a running Pulse server.
+- **Unix installation handles existing permissions.** Generated commands recognise passwordless sudo. Non-root preflight no longer fails merely because the saved installer directory requires root access.
+- **Agent names survive profile migration.** Moving to the safe profile preserves the hostname already reported instead of replacing it with a fully qualified name.
+- **Updates finish more reliably.** The agent version endpoint matches the executable's version format. Successful automatic server updates finish without waiting on an unsupported notification request.
+- **Manual update helpers remain usable.** Replacement avoids truncating a running script, and preparation failures preserve existing helpers. Bootstrap downloads have deadlines and require HTTPS through redirects.
+- **Installer guidance keeps tokens private.** Examples use a private token file and a downloaded installer users can inspect, with clearer privilege and cleanup instructions.
+- **NAS upgrades preserve other startup jobs.** Unraid and QNAP updates replace recognised Pulse entries while retaining unrelated boot commands. Unrecognised arrangements stop with recovery files retained.
+- **Unraid removal protects active boot scripts.** Agent uninstall refuses to proceed while an unrelated live boot shell could be affected.
+- **Legacy cleanup preserves recovery access.** Cleanup requires complete inventory, preserves shared SSH key targets, and retains recovery keys when local cleanup cannot finish.
+- **New Proxmox installs leave existing guests alone.** Creating Pulse no longer performs legacy mount cleanup on other LXCs. Failed or interrupted installs retain the new container for inspection and recovery.
+- **Failed removals preserve recovery data.** Server removal retains configuration until earlier removal steps succeed. Windows agent removal keeps identity, credentials, logs and binaries until server unregistration is confirmed.
+- **Update and removal failures are clearer.** Agent help distinguishes download, validation and activation failures before another attempt. Unattended Windows removal errors return without waiting for a dialogue.
+
+## Pulse Pro, AI and hosted
+
+- **Patrol opens the right resource.** Inbox alerts, findings and actions use consistent resource identities. Findings repeating an alert group under that specific alert, while separate problems retain their own decisions.
+- **Resource filters cover the whole Patrol view.** Open work counts, filter badges, approvals and summaries match the resource being browsed.
+- **Active Docker problems stay open.** Patrol skips resolution reviews when current container evidence still shows the fault. Missing condition readings or healthy unrelated metrics cannot imply recovery.
+- **Demo findings match their resources.** Demo Patrol findings appear in the corresponding resource views and group with matching alerts.
+- **Workspace agent enrolment works consistently.** Install tokens live where agents authenticate. Registration, diagnostics, command permissions and revocation use the same organisation-bound records.
+- **Workspace recovery stays isolated.** Imports reload only the selected organisation, preserve instance-wide settings, and avoid copying another workspace's connections or credentials.
+- **MSP billing respects cancellation.** The Plan page points to Manage billing for renewal or end dates. The guide explains self-service purchasing, upgrades and applying a purchase.
+
+## Monitoring and service health
+
+- **Restarted servers show agents awaiting reports.** Machines, Infrastructure and resource drawers distinguish saved enrolment from fresh telemetry until the first valid report arrives.
+- **Silent agents stop supplying live values.** Expired reporting stops cached readings from appearing current in charts. Stored history remains available, and open drawers refresh when reporting stops or resumes.
+- **Incomplete guest status is rejected.** Proxmox responses missing usable status or identifying the wrong guest cannot supply monitoring readings or action checks.
+- **Cluster links open the right node.** Discovered members use their reported Proxmox address when a short hostname would be unsuitable for the browser.
+- **Startup handles duplicate clusters earlier.** Consolidation finishes before monitoring becomes available, avoiding conflicts with agent registration.
+- **Expired backup scans stop promptly.** Storage scans stop when their time budget expires or monitoring stops, instead of continuing retries across remaining nodes.
+- **Mail Gateway queues show real totals.** Counts come from Postfix queue summaries. Delay estimates use the oldest reported age band and exclude intentionally held mail.
+- **Mail Gateway read failures stay specific.** Failed optional reads no longer throttle the whole connection. Reachable gateways with missing readings show Degraded, and decoding failures remain distinct from network outages.
+- **Mail Gateway help explains collection controls.** Guidance clarifies which saved switches stop reads and why disabling a failing read removes coverage rather than repairing it.
+
+## Security
+
+- **CSV text stays text in spreadsheets.** Reports, VM inventory and audit exports protect supplied names and other text from becoming formulas. Audit checks and JSON exports continue using the original event data.
+- **Workspace tokens use current permissions.** Requests recheck the live organisation token store after configuration changes or revocation. An invalid explicit token cannot fall through to browser-session access.
+- **Agent access requires appropriate permissions.** Non-admin browser and proxy users cannot submit telemetry, acknowledge Docker commands or read agent configuration containing probe credentials. Scoped agent tokens retain their intended access.
+- **Compressed messages have a size limit.** Pulse bounds decompressed incoming WebSocket messages before buffering them, reducing exposure to oversized compressed input.
+- **Administrative requests must be unambiguous.** SSO, access recovery and audit requests reject conflicting fields or malformed selections. Removing all audit destinations requires an explicit empty list.
+- **Audit exports have a clear limit.** Exports and summaries reject selections above 10,000 events instead of returning partial results. Narrow the time range, event type or user.
+- **SSO edits preserve protected settings.** Ordinary provider edits retain advanced options the editor cannot display. Environment-managed providers cannot be replaced, removed or taken over through saved settings.
+- **SSO tests describe their limits.** OIDC requires the same issuer match as sign-in, including trailing slashes. SAML checks require an identity and usable SSO URL. Neither test claims to have completed sign-in.
+- **SSO errors preserve useful drafts.** Failed saves give readable guidance without automatic write retries. OIDC tests and SAML previews keep private responses out of errors, and preview failures restore focus.
+- **Local-login help explains the limit.** Hiding the password form does not disable local password authentication or enforce SSO-only access. Guidance clarifies the separate administrator recovery path.
+- **Cluster certificate trust is editable per endpoint.** Settings lets users inspect, test and save trust for existing PVE polling endpoints while preserving other members' trust and disabled collection settings.
+- **OIDC verification is hardened.** Updated key and token verification dependencies address security flaws and bound oversized RSA key input.
+
+## Other improvements
+
+- **Configuration recovery saves related data together.** Guest metadata commits with settings and credentials. Failed writes restore previous files and preserve older recovery backups instead of leaving a partial replacement.
+- **Repeated imports cannot overwrite newer edits.** Concurrent imports are blocked per workspace, and recently submitted backups are temporarily blocked from being applied again.
+- **Transfers stay with the confirmed workspace.** Export and import dialogs show the workspace ID and stop if selection changes. Feedback stays beside the inputs, and saving a token does not repeat the transfer.
+- **Saved and applied are distinguished.** Import failures identify components that did not reload. Uncertain responses warn that changes may already have applied and advise inspecting the destination before repeating the import.
+- **Recovery explains its limits before transfer.** Settings identifies configuration exports as partial backups. Migration guidance covers excluded data, access requirements, isolated trials, retained storage and monitoring handover.
+- **Backup help explains conflicting readings.** Guidance separates inventory entries, completed points, daily volume, task outcomes and guest placement, helping users compare existing records without starting another backup.
+- **Unavailable inventory fails clearly.** Manual and scheduled VM inventory exports report unavailable source data instead of producing a successful empty download.
+- **Missing web assets return proper errors.** Missing scripts, styles and documentation return Not Found instead of a successful response containing the application page.
+- **Update guidance distinguishes policy from availability.** Help explains that an approved stable-patch policy or a merged fix does not mean an update has been published.
+
+## Known issues
+
+- **Guest safety remains unresolved.** These changes do not confirm a fix for every guest freeze or Windows restart. If monitoring was stopped after a guest froze, do not restart it solely to test this beta or this release.
+- **Affected backups still need precautions.** Stop Pulse monitoring before a freeze-enabled backup. Keep it stopped until independent checks confirm thaw, fresh writes on every backed-up filesystem and workload liveness. An OK task does not prove thaw.
+- **Kubernetes pauses need controller and storage checks.** Confirm retained server storage before stopping pods, and prevent controllers from replacing them. Deleting a pod or stopping only the collector does not confirm server polling has stopped.
+- **Elevated server memory remains unresolved.** Reduced chart overhead does not establish a lower long-running baseline. Keep the working setup and report elevated steady usage or continued growth from existing readings at comparable uptimes and workloads.
+
+## Before you upgrade
+
+- Windows Unified Agent binaries are not Authenticode-signed while SignPath remains unavailable and may show an Unknown Publisher warning. Verify downloads with the published checksums and detached signatures.
+- Pulse Mobile is being retired on 31 March 2027. It keeps working until then. For alerts on your phone afterwards, add an ntfy, Gotify, or Pushover destination, and open Pulse in your phone's browser. Relay is no longer sold, and existing Relay subscribers now have Pro features at their current price. This candidate does not require a companion mobile release.
+- The rollback target is stable `v6.6.0`. On systemd and Proxmox LXC installs, use this command only when `/bin/update` was installed by the Pulse server installer: `sudo /bin/update --version v6.6.0` to return to the previous stable release. For Docker Compose, pin `rcourtman/pulse:6.6.0` and recreate the container.
diff --git a/docs/releases/RELEASE_NOTES_v6.7.0-beta.3.md.visuals.json b/docs/releases/RELEASE_NOTES_v6.7.0-beta.3.md.visuals.json
new file mode 100644
index 0000000000..dc2038ee88
--- /dev/null
+++ b/docs/releases/RELEASE_NOTES_v6.7.0-beta.3.md.visuals.json
@@ -0,0 +1,5 @@
+{
+ "schema_version": 1,
+ "captures": [],
+ "decision": "Zero captures: the notes describe the changes in text."
+}
diff --git a/docs/releases/V6_CHANGELOG_v6.7.0-beta.3.md b/docs/releases/V6_CHANGELOG_v6.7.0-beta.3.md
new file mode 100644
index 0000000000..2b5d77fb8b
--- /dev/null
+++ b/docs/releases/V6_CHANGELOG_v6.7.0-beta.3.md
@@ -0,0 +1,251 @@
+# Pulse v6.7.0-beta.3
+
+This changelog describes the changes since `v6.6.0`. Stable `v6.6.0` remains the rollback target.
+
+## Changes since v6.6.0
+
+- Fail closed on missing backend CI admission (#3452)
+- Keep real runtime data disks visible in filesystem monitoring (#3450)
+- Keep keyboard focus through Backups read recovery (#3448)
+- Explain missing real filesystems without changing guest storage (#3449)
+- Keep server recovery data until removal has completed (#3447)
+- Keep the assessed Backups view stable through health refreshes (#3446)
+- Keep running backup files scoped to their local disk (#3445)
+- Explain Docker runtime and container alert scopes (#3443)
+- Keep failed Proxmox installs available for recovery (#3441)
+- Remove inert runtime alert switches and explain their supported scope (#3442)
+- Bound the OIDC JOSE security graph without changing storage dependencies (#3440)
+- Explain why a usage alert stays open after readings fall (#3438)
+- Keep new Proxmox installs out of existing guest maintenance (#3436)
+- Keep backup activity focus and readings current across polling (#3437)
+- Keep explicitly unknown PVE archives off guest protection (#3435)
+- Clarify protection scope beside location-filtered backup evidence (#3434)
+- Release completed backend slice slots to ordinary packages (#3431)
+- Keep narrow Coverage workload identity readable (#3430)
+- Split slow backend suites without weakening required checks (#3427)
+- Reject ambiguous dates in backup protection assessments (#3428)
+- Keep uncertain backup evidence inspectable in Coverage (#3426)
+- Report SAML metadata evidence without implying tested sign-in (#3424)
+- Explain missing backup placement without confusing repository identity (#3421)
+- Keep unattended Windows removal failures recoverable (#3423)
+- Keep Workloads backup completions on the strict timestamp path (#3422)
+- Keep audit CSV text literal without rewriting signed evidence (#3420)
+- Keep malformed backup timestamps out of ages and task order (#3419)
+- Exercise Windows uninstall boundaries with LF and CRLF source (#3418)
+- Keep OIDC Test HTTP failures private and actionable (#3417)
+- Retain backup task origin independently of current guest placement (#3415)
+- Retain Windows agent recovery state until unregistration is confirmed (#3414)
+- Preserve advanced SSO settings across ordinary provider edits (#3413)
+- Explain backup task failures and uncertain ordering in Recovery Help (#3412)
+- Keep backup repository hints out of guest node attribution (#3411)
+- Release v6.7.0-beta.2 (#3410)
+- Keep indeterminate backup task order from claiming a latest OK (#3406)
+- Regress unsupported updater completion notifications (#3407)
+- Distinguish approved stable patches from available updates in Help (#3408)
+- Bound decompressed WebSocket messages before buffering
+- Make OIDC Test require the same issuer identity as sign-in (#3404)
+- Expose latest backup failure evidence in workload Coverage (#3403)
+- Admit reconstructible stable patches on version-bound release branches (#3402)
+- Explain PMG collection controls in the published stable release (#3401)
+- Apply managed Proxmox TLS trust to exact polling endpoints (#3400)
+- Keep backup workload scope visible across cluster namesakes (#3399)
+- Identify backup connections in restore-point evidence (#3397)
+- Explain agent update failures before another manual attempt (#3396)
+- Explain successful PVE tests alongside rejected cluster polling (#3394)
+- Align the E2E bootstrap seed with the governed Alpine runtime (#3392)
+- Keep SAML metadata preview failures private and actionable (#3393)
+- Keep retained PVE archives bound to their guest kind (#3391)
+- Refresh governed Node and Alpine container digests together (#3390)
+- Distinguish local-login hiding from SSO-only enforcement (#3388)
+- Expose prune retention hiding backup verification (#3386)
+- Classify PVE backup guests from artifact paths, not storage labels (#3377)
+- Respect label identities during issue classification (#3378)
+- Reproduce unknown backup sizes hiding completed activity (#3376)
+- Preserve case-insensitive issue label identities (#3375)
+- Preserve operator boot jobs during Unraid agent upgrades (#3374)
+- Isolate metadata projection parity from live mock ticks (#3373)
+- Explain filtered backup activity without changing protection policy (#3372)
+- Preserve unrelated QNAP startup jobs during agent upgrades (#3371)
+- Keep identical local backup paths independent across PVE nodes (#3369)
+- Scope backup activity to the displayed inventory filters (#3368)
+- Respect visible legacy version labels in issue intake (#3367)
+- Cover keyboard access to retained delivery activity (#3366)
+- Stop expired backup storage scans before retrying more nodes (#3365)
+- Fix cleanup fixture confinement through directory aliases (#3364)
+- Protect agent reporting and configuration authority
+- Cover readable single-attempt SSO save recovery (#3363)
+- Keep disabled local backup disks scoped to their node (#3361)
+- Preserve recovery keys when local legacy cleanup cannot complete (#3359)
+- Keep unread PBS namespaces in the live backup inventory (#3357)
+- Keep backup evidence stable through native scrolling and polling (#3356)
+- Reconcile same-second comments before restoring topic reviews (#3358)
+- Require complete inventory for legacy credential cleanup (#3355)
+- Keep unread local backup files scoped to their storage node (#3353)
+- Respect topic reviews cleared since the queued issue event (#3354)
+- Keep backup activity on local calendar dates across clock changes (#3352)
+- Preserve review tasks across repeated topic fields (#3351)
+- Balance isolated smoke suites with measured scheduling hints (#3350)
+- Preserve environment SSO authority across extension saves (#3348)
+- Preserve issue declarations through formatted field headings (#3349)
+- Keep backup-location filters scoped to one repository (#3347)
+- Show partial backup history as attention, not unknown (#3346)
+- Count node-restricted backup storage as read when another node lists it (#3344)
+- Keep long version declarations from aborting issue triage (#3345)
+- Bound synchronous audit exports and summaries (#3343)
+- Cancel protection assessment batches with their consuming read (#3342)
+- Require complete Proxmox guest status observations (#3341)
+- Recover lifecycle discovery from peer stream cancellation (#3340)
+- Reject malformed backup protection assessments (#3339)
+- Confine release credentials to the release environment (#3303)
+- Hide macOS Time Machine mounts from agent disk inventory (#3338)
+- Keep non-root agent preflight outside saved installer trust (#3337)
+- Keep mounted backup evidence and badge tones current (#3336)
+- Show a partial PMG read as degraded, not unreachable (#3333)
+- Scope TrueNAS release notes to the delivered fixes (#3332)
+- Separate PMG decoding failures from gateway reachability (#3329)
+- Keep failed optional PMG reads from throttling the connection (#3327)
+- Release v6.7.0-beta.1 (#3328)
+- Add an interaction stability probe for hover and live readouts (#3326)
+- Keep the drawer History readout still while scrubbing (#3325)
+- Read PMG queue counts from qshape, not the queue index (#3324)
+- Preserve existing Docker deployments during setup (#3323)
+- Keep TrueNAS protection evidence readable on phones (#3322)
+- Reject incomplete Proxmox storage inventories (#3321)
+- Keep agent installer guidance off token arguments and HTTP pipes (#3320)
+- Keep topic review through comments during metadata preparation (#3319)
+- Reject incomplete Proxmox snapshot response inventories (#3318)
+- Keep empty Coverage evidence scoped to the current list (#3316)
+- Preserve topic review when a comment precedes intake (#3315)
+- Stop container continuity reads at explicit access refusals (#3314)
+- Make platform sort headings usable from the keyboard (#3313)
+- Preserve PVE snapshot history across incomplete reads (#3312)
+- Keep concurrent reports from losing issue metadata (#3311)
+- Keep unread vzdump guest logs from renewing running state (#3310)
+- Keep TrueNAS start and running dates out of completed evidence (#3309)
+- Do not renew PBS point evidence from failed-read cache rows (#3308)
+- Expose failed TrueNAS protection refreshes beside retained events (#3307)
+- Keep undated TrueNAS replication failures visible (#3306)
+- Explain saved and uncertain configuration import failures (#3304)
+- Keep undated TrueNAS snapshots from inventing backup freshness (#3302)
+- Show alert history rows without repeating the resource (#3301)
+- Report incomplete configuration recovery without false success (#3298)
+- Preserve updater assets when repository configuration fails (#3299)
+- Recover activation for release-train snapshot runs (#3297)
+- Align triage disclosure with current release and retest policy (#3296)
+- Wait for Docker update health checks before verifying (#3294)
+- Accept release-dispatch refs as post-merge snapshot dispatches (#3295)
+- Keep Alert History rows on one line on desktop (#3293)
+- Sync issue labels with GITHUB_TOKEN, not the triage App key (#3292)
+- Keep Machines, thresholds and infrastructure rows on one line (#3286)
+- Reset guest shadow runs on healthy powered-state observations (#3289)
+- Explain the limits of TrueNAS protection evidence (#3290)
+- Mark the proposed refund programme withdrawn (#3291)
+- Fail closed when local pre-push source reads fail (#3288)
+- Stop promising renewal on a cancelled MSP plan (#3285)
+- Let NOPASSWD sudo users run the agent install command (#3283)
+- Record individual-request-only transition remedies (#3284)
+- Keep migration trials isolated until monitoring handover (#3282)
+- Restore CORE reporting and native History on current main (#3281)
+- Explain controller-aware backup safety for Kubernetes servers (#3279)
+- Finish PVE startup consolidation before publishing monitors (#3278)
+- Keep signed manual update bootstraps on HTTPS (#3275)
+- Track annual transition refund exit preparation (#3277)
+- Explain local PVE backup and Coverage disagreements (#3274)
+- Keep reading cues and container actions on one row line (#3276)
+- Restart PBS metric timing after node-status gaps (#3273)
+- Record Community transition refund preparation (#3271)
+- Clear ended Proxmox backup activity from resource snapshots (#3269)
+- Reuse chart point selection for identical metric timelines (#3267)
+- Store tenant agent install tokens where agents authenticate (#3268)
+- Reuse one Markdown snapshot per issue metadata decision (#3270)
+- Keep phone platform table rows on one line (#3266)
+- Replace manual update helpers without truncating running readers (#3265)
+- Keep declared server versions separate from image aliases and companions (#3264)
+- Encode Proxmox broadcast records without per-field maps (#3263)
+- Identify backup provider scopes in Coverage evidence (#3262)
+- Point the MSP guide at v6.6.0 and self-serve buying (#3261)
+- Interpret byte-throughput benchmark changes in the right direction (#3260)
+- Keep configuration-transfer feedback in its active dialog (#3259)
+- Keep future backup dates out of current protection (#3258)
+- Keep phone guest rows on one line with the backup shield (#3256)
+- State configuration recovery's limits before transfer (#3255)
+- Keep canonical protection aligned with recognised Proxmox subjects (#3254)
+- Do not infer failing versions from upgrade transitions (#3253)
+- Keep isolated issue-triage changes on their dedicated CI path (#3252)
+- Fix cluster member links and safe-profile hostnames (#3251)
+- Prevent configuration-import replays from overwriting newer edits (#3250)
+- Release v6.6.0 (#3247)
+- Preserve document reference links during issue classification (#3246)
+- Bind configuration transfers to their confirmed workspace (#3245)
+- Reproduce partial recovery when guest metadata cannot be imported (#3244)
+- Bound signed manual-update bootstrap downloads (#3243)
+- Keep feedback classification bound to the visible selection (#3242)
+- Reproduce destructive acceptance of incomplete configuration backups (#3240)
+- Keep unavailable VM inventory out of successful downloads (#3239)
+- Reduce workload chart overhead and repair browser test setup (#3233)
+- Reproduce tenant configuration import runtime contamination (#3238)
+- Keep report CSV text from becoming spreadsheet formulas (#3237)
+- Keep local safety checks effective on large staged changes (#3236)
+- Keep formatted empty responses out of topic review (#3235)
+- Return real not-found responses for missing frontend assets (#3231)
+- Keep feature-request context out of secondary-topic review (#3232)
+- Fix accessible controls, resource provenance and deep drawer scrolling (#3222)
+- Run isolated installer safety controls within Go's parallel budget (#3230)
+- Clarify the target and authority for configuration recovery (#3229)
+- Require observed capacity for storage warnings (#3228)
+- Explain completed backup counts without losing incomplete evidence (#3227)
+- Keep platform and agent versions out of title triage (#3226)
+- Keep unavailable Proxmox node disks from resolving warnings (#3225)
+- Keep neighbouring issue fields out of topic review (#3223)
+- Keep unavailable agent filesystems from resolving disk alerts (#3221)
+- Keep backup layout checks aligned with completed restore points (#3220)
+- Recognise declared Pro server artifacts during issue intake (#3219)
+- Keep incomplete backup entries out of completed restore totals (#3218)
+- Keep absent host disk readings out of live charts and history (#3217)
+- Keep a real change out of the Highlights example (#3216)
+- Show agents awaiting a report after server restart (#3214)
+- Show agents awaiting a report after server restart (#3211)
+- Complete managed npm graph refresh on counted-navigation repair (#3213)
+- Decode native retained metric numbers without per-point reflection (#3212)
+- Keep deleted webhook work bound to its original destination (#3210)
+- Patch portal Vitest and preserve counted navigation names (#3209)
+- Patch portal development dependency advisories (#3206)
+- Assemble retained metric series directly by statement-local number (#3205)
+- Prove demo auto sign-in in the public browser smoke (#3204)
+- Make release Highlights name concrete changes (#3203)
+- Name demo Patrol findings by their unified resource (#3202)
+- Show post-update What's New as a plain changelog (#3201)
+- Move demo deploys to the tag:ci-deploy Tailscale client (#3200)
+- Keep bounded hosted provisioning overhead in chart SLO verdicts (#3199)
+- Transport filtered retained metrics by statement-local series number (#3198)
+- Treat a deleted convergence owner as terminal (#3197)
+- Re-dispatch Pro promotion refused by a moved pulse-pro main (#3193)
+- Make synthetic log-reader survival failures attributable (#3195)
+- Scope the Patrol Open work summary to the browsed resource (#3194)
+- Reject competing audit webhook destination fields (#3192)
+- Refuse Unraid uninstall while the rc.local go shell is live (#3191)
+- Reject competing audit webhook destination fields (#3190)
+- Keep Settings actions visible and browser fixtures isolated (#3189)
+- Name Patrol inbox alert subjects by their unified resource (#3188)
+- Stop Patrol resolving Docker alerts the snapshot still shows (#3187)
+- Bump actions/create-github-app-token from 3.2.0 to 3.3.0 in the actions-minor-patch group (#3182)
+- Reconcile the separated metrics and HTTP dependency graph (#3184)
+- Keep missing vzdump guest verdicts unknown (#3183)
+- Separate storage runtime dependency proposals from other Go patches (#3180)
+- Preserve explicit audit selections before reads and webhook updates (#3179)
+- Withdraw failed backup protection assessments (#3177)
+- Reconcile the non-storage managed Go dependency refresh (#3176)
+- Release v6.6.0-rc.6 (#3175)
+- Verify complete bounded backup posture batches for large estates (#3174)
+- Keep unread disabled backup storage out of complete PVE history (#3173)
+
+## Release Metadata
+
+- Version: `v6.7.0-beta.3`
+- Previous candidate: `v6.7.0-beta.2`
+- Previous stable: `v6.6.0`
+- Rollback target: `v6.6.0`
+- Rollback command: `sudo /bin/update --version v6.6.0`
+- Promotion path: exact-SHA single-build release candidate from `main`
+- Windows signing decision: prereleases publish checksum- and detached-signature-verified Windows agents without Authenticode while SignPath remains unavailable. Windows Unified Agent binaries may display an Unknown Publisher warning
+- Mobile decision: `no-mobile-impact`. No governed mobile route, payload, Relay, pairing, approval, push or onboarding contract changed from `v6.6.0`, so no companion mobile build or store rollout is required
diff --git a/frontend-modern/public/docs/UPGRADE_v6.md b/frontend-modern/public/docs/UPGRADE_v6.md
index fe5b746960..ca6c789731 100644
--- a/frontend-modern/public/docs/UPGRADE_v6.md
+++ b/frontend-modern/public/docs/UPGRADE_v6.md
@@ -9,8 +9,8 @@ public Community downloads do not replace a private Pro build.
For the current v6 beta packet, see:
-- `docs/releases/RELEASE_NOTES_v6.7.0-beta.2.md`
-- `docs/releases/V6_CHANGELOG_v6.7.0-beta.2.md`
+- `docs/releases/RELEASE_NOTES_v6.7.0-beta.3.md`
+- `docs/releases/V6_CHANGELOG_v6.7.0-beta.3.md`
For the current stable v6 packet, see:
diff --git a/scripts/install-docker.sh b/scripts/install-docker.sh
index b778eec692..1748894800 100755
--- a/scripts/install-docker.sh
+++ b/scripts/install-docker.sh
@@ -6,7 +6,7 @@ set -euo pipefail
SCRIPT_DIR="$(CDPATH= cd -- "$(dirname -- "$0")" && pwd)"
DOCKER_IMAGE_REPO="${DOCKER_IMAGE_REPO:-rcourtman/pulse}"
-CANONICAL_DEFAULT_PULSE_VERSION="6.7.0-beta.2"
+CANONICAL_DEFAULT_PULSE_VERSION="6.7.0-beta.3"
resolve_default_pulse_version() {
if [ -n "${PULSE_IMAGE_VERSION:-}" ]; then