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.
Go aialertsdashboarddockerdocker-monitoringgohomelabinfrastructure-monitoringkubernetesmonitoringmspproxmoxproxmox-backup-serverproxmox-mail-gatewayproxmox-veself-hostedtruenastypescriptvspherewebhooks
Prepare v6.7.0-rc.1
pulse-triage[bot]73ad6c7f20fa
diff --git a/VERSION b/VERSIONindex d9ea631b1c..ced616ded8 100644--- a/VERSION+++ b/VERSION@@ -1 +1 @@-6.7.0-beta.3+6.7.0-rc.1diff --git a/deploy/helm/pulse/Chart.yaml b/deploy/helm/pulse/Chart.yamlindex 47d4b8255f..961d8d56d8 100644--- a/deploy/helm/pulse/Chart.yaml+++ b/deploy/helm/pulse/Chart.yaml@@ -2,9 +2,9 @@ apiVersion: v2name: pulsedescription: Helm chart for deploying the Pulse hub and optional Docker, Kubernetes, or OpenShift monitoring agent.type: application-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+version: 6.7.0-rc.1+appVersion: "6.7.0-rc.1"+icon: https://raw.githubusercontent.com/rcourtman/Pulse/v6.7.0-rc.1/docs/images/pulse-logo.svgkeywords:- monitoring- proxmox@@ -32,7 +32,7 @@ annotations:description: Smoke tests with kind cluster deploymentartifacthub.io/links: |- name: Documentation- url: https://github.com/rcourtman/Pulse/blob/v6.7.0-beta.3/docs/KUBERNETES.md+ url: https://github.com/rcourtman/Pulse/blob/v6.7.0-rc.1/docs/KUBERNETES.md- name: Supporturl: https://github.com/rcourtman/Pulse/discussionsartifacthub.io/maintainers: |diff --git a/deploy/helm/pulse/README.md b/deploy/helm/pulse/README.mdindex 9987ee93c9..ea358d9ad2 100644--- a/deploy/helm/pulse/README.md+++ b/deploy/helm/pulse/README.md@@ -1,6 +1,6 @@# pulse-  +  Helm chart for deploying the Pulse hub and optional Docker, Kubernetes, or OpenShift monitoring agent.diff --git a/docker-compose.yml b/docker-compose.ymlindex 48afc7ac47..ef112cd3a9 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.3}+ image: ${PULSE_IMAGE:-rcourtman/pulse:6.7.0-rc.1}container_name: pulserestart: unless-stoppedlogging:diff --git a/docs/RELEASE_NOTES.md b/docs/RELEASE_NOTES.mdindex 90fc694a69..3ee17f3fdc 100644--- a/docs/RELEASE_NOTES.md+++ b/docs/RELEASE_NOTES.md@@ -6,9 +6,9 @@ Pulse release notes live on GitHub: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.3.md`-- `docs/releases/V6_CHANGELOG_v6.7.0-beta.3.md`+For the current v6 release candidate packet, see:+- `docs/releases/RELEASE_NOTES_v6.7.0-rc.1.md`+- `docs/releases/V6_CHANGELOG_v6.7.0-rc.1.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.mdindex ca6c789731..f78c173c5b 100644--- a/docs/UPGRADE_v6.md+++ b/docs/UPGRADE_v6.md@@ -7,10 +7,10 @@ Choose an actually [published software release](https://github.com/rcourtman/Pulnot a draft, source tag or Helm-chart asset. Keep the existing runtime edition:public Community downloads do not replace a private Pro build.-For the current v6 beta packet, see:+For the current v6 release candidate packet, see:-- `docs/releases/RELEASE_NOTES_v6.7.0-beta.3.md`-- `docs/releases/V6_CHANGELOG_v6.7.0-beta.3.md`+- `docs/releases/RELEASE_NOTES_v6.7.0-rc.1.md`+- `docs/releases/V6_CHANGELOG_v6.7.0-rc.1.md`For the current stable v6 packet, see:diff --git a/docs/releases/RELEASE_NOTES_v6.7.0-rc.1.md b/docs/releases/RELEASE_NOTES_v6.7.0-rc.1.mdnew file mode 100644index 0000000000..c81ab2d735--- /dev/null+++ b/docs/releases/RELEASE_NOTES_v6.7.0-rc.1.md@@ -0,0 +1,172 @@+# Pulse v6.7.0-rc.1 Release Notes++This release candidate opens the `v6.7.0` candidate line after stable `v6.6.0`, which remains the rollback target.++Pulse v6.7.0 makes backup status clearer when reads fail, dates are uncertain or tasks disagree. It strengthens configuration recovery, restores TrueNAS CORE readings, reduces chart processing and lets external agents read fleet changes and metric history.++## Highlights++- Proxmox Backups now counts completed restore points separately from running and failed entries.+- TrueNAS CORE monitoring now loads CPU, memory and History readings previously blocked by rejected reporting requests.+- Settings Recovery now rejects incomplete configuration backups before they can replace existing settings.++## What's improved++- **Charts need less processing.** Workload history uses less decoding, copying and temporary memory. Proxmox live updates also create fewer temporary objects.+- **History stays steady while browsing.** Drawer charts reserve room for changing values and times. Peak labels stay beside plotted spikes and identify peaks above the plotted average.+- **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.** Backups updates readings and badge colours while preserving filters, expanded details, scroll position and chart focus. Keyboard focus follows the inspected point through sorting, date regrouping and failed reads.+- **Rows and details stay readable.** Machines, Workloads, Infrastructure, thresholds and platform tables keep status cues and actions compact. Detail tables fit their drawer or split pane.+- **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.+- **Sorting works from the keyboard.** Platform table headings have focusable sort buttons that respond to Enter and Space. Backup summary buttons no longer toggle twice with Space.+- **SSO addresses stay readable.** Settings keeps complete callback, metadata and ACS URLs beside their copy controls within the panel.+- **Dark labels have clearer contrast.** Muted text is 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.+- **Connection failures preserve saved access.** Startup keeps credentials and workspace selection when discovery fails. Sign-in offers a read-only retry, and public Help stays reachable during session-check failures.+- **Polling logs are quieter and more private.** Routine PBS datastore readings move to debug logging. Failed-response diagnostics record response size instead of copying provider contents into logs.++## Alerts and notifications++- **Alert History avoids repeated names.** Rows show the condition beside the resource without 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. Unread destination settings block replacement until they can be loaded.+- **Delivery activity supports keyboard browsing.** The notification log can be focused and scrolled, and refreshes preserve keyboard position.+- **PBS alert timing restarts after gaps.** Missing CPU or memory readings interrupt activation and recovery timing without clearing existing warnings.+- **Rolling alerts use the right history.** Averaged alerts find their own stored readings for host agents, Docker hosts and containers, and Proxmox LXCs, including resources combined with another monitoring source.+- **Docker alert controls show their scope.** Thresholds removes ineffective runtime switches. Help explains that Offline Alerts covers runtime connectivity, while containers have separate settings.+- **Recovery rules are clearer.** 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 excluding container layers. Help explains missing mounts without asking users to move data.+- **Disk totals avoid counting aliases twice.** Workloads summaries use the supplied aggregate capacity when available. Individual mount readings and warning colours remain inspectable.+- **Disk cards show the correct percentage.** Resource disk summaries no longer interpret a usage ratio as an already calculated percentage.+- **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 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 a warning still takes effect.+- **macOS excludes 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. Failed reads, disabled storage and running files stay scoped to the correct local disk.+- **Archives and snapshots protect the right guest.** PVE archive paths identify VM and LXC backups. Reused VMIDs, conflicting file IDs, retained snapshots and unknown archive types cannot give another guest protection credit.+- **Backup locations keep their boundaries.** Similar repositories on different connections stay separate. Restore evidence names its reading connection, while notices explain that location filters do not recalculate workload-wide protection.+- **Guest SMART failures stay visible.** A failed scoped read hides cached SMART values instead of presenting them as current. Closing and reopening the drawer preserves the error and recovery path.+- **Linux temperatures exclude other sensor units.** Fan RPM, voltage and power no longer become Celsius readings. Help shows where existing extra temperatures and fans appear in Machine or Host details, without promising per-sensor alerts.++## Proxmox, PBS and backups++- **Incomplete reads preserve inventory.** Failed, partial or malformed PVE and PBS listings cannot erase retained entries. PBS checks datastore, namespace, group, snapshot and file identities before reconciling history.+- **Access refusals remain meaningful.** Backup collection stops continuity reads after explicit permission refusals. A readable sibling namespace cannot establish that an unread namespace is empty, and access warnings persist until enumeration recovers.+- **Old evidence cannot become fresh again.** Retained PVE snapshots and cached PBS backups from failed reads no longer renew protection evidence. Accepted listings survive later timeouts, throttling and optional size-read failures.+- **Failed assessments withdraw outdated claims.** Coverage rejects failed, malformed, duplicate or inconsistent results and offers Retry. Large fleets use complete batches with limited parallel requests, cancelled when leaving the view.+- **Uncertain evidence remains inspectable.** Coverage keeps restore details when assessments fail and distinguishes partial history from no backups. Provider reads, job results and restore-point states have separate labels explaining their limits.+- **Backup identities and dates are visible.** Coverage and By date show native restore-point IDs, locations and reported timestamps without hovering. Coverage also shows assessment, latest-success and verification times.+- **Uncertain dates cannot imply protection.** Ages, completion labels and verification summaries reject malformed or ambiguous dates. Future dates stay uncertain and identify clocks to check, while recognised older guest IDs still match Coverage.+- **Backup activity follows the evidence.** Completed jobs clear running indicators. Missing guest results stay Unknown, conflicting task results cannot complete archives, and unread writer lists cannot declare backups failed.+- **Activity follows inventory filters.** Search, node, type, source, location and verification filters narrow the chart. Day selection narrows only the list, and calendar dates remain correct across clock changes.+- **Unknown sizes and retention stay distinct.** Charts mark completed points with unknown sizes and show known volume, while restore details distinguish unknown size from zero. Prune retention stays separate from verification, including Not reported.+- **Task failures have inspectable details.** Coverage shows outcomes, errors, IDs and original task location, including migrated guests. Missing durations stay unknown, uncertain ordering keeps possible latest tasks visible, and Show more limits long lists.+- **Cluster trust is editable per endpoint.** Settings lets users inspect, test and save certificate trust for existing PVE polling addresses. Other members' trust and disabled collection settings are preserved, and tests identify the address checked.++## TrueNAS, vSphere and Docker++- **CORE memory separates Free and ARC correctly.** Compatible TrueNAS CORE 13 systems supply both values from one authenticated native reading instead of combining differently timed measurements.+- **Memory composition is accessible.** The TrueNAS Overview memory bar opens a breakdown with the keyboard or a click. Help explains Used, reclaimable ARC cache and Free.+- **CORE disk throughput reaches History.** TrueNAS Storage retains physical-disk read and write rates through charts and stored history. Help distinguishes individual disk activity from host totals and capacity.+- **History finds the correct source.** TrueNAS and vSphere drawers preserve the provider's history identity when loading through the resource API.+- **Protection dates reflect completed work.** Collection time no longer becomes snapshot creation time, including older records. Start times, running replication and malformed dates 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.+- **Unread protection history stays distinct from empty.** TrueNAS Protection rejects malformed or duplicate records, warns when showing retained events and offers Refresh. Help explains snapshot and replication limits.+- **Docker updates wait for health checks.** Pulse waits up to three minutes for replacement containers' initial checks and detects restarting containers. Verification stays inconclusive while health is still starting.+- **Image checks follow local replacements.** Docker refreshes cached tag information when a new local image needs comparison, while respecting registry backoff. Manual checks discard older in-flight results rather than restoring stale cache entries.+- **Image-check failures open their details.** Docker Images makes Check failed a keyboard-accessible button, so errors can be read without hovering.+- **Private registry setup is clearer.** Docker Help explains HTTPS requirements, agent-local login files and credential helpers, container mounts and login caching. It distinguishes pulls, anonymous checks and cached update results.+- **Docker credentials get safer setup guidance.** Authentication-file examples refuse symlinks and non-regular files, preserve existing contents and restore private permissions before launch.++## Install, updates and agents++- **Docker setup preserves existing deployments.** The helper stops when Compose configuration already exists, protecting custom ports, mounts, image pins and credentials.+- **Docker images avoid repeated large files.** Server packaging no longer stores another copy of binaries just to change permissions. Help distinguishes image layers from retained Pulse data without asking users to delete data.+- **Installation success requires startup.** The server installer stops on directory-setup failures and confirms startup before reporting success. Help distinguishes prepared configuration, a running service and a usable dashboard.+- **Agent installer files arrive together.** Server installation publishes the served agent scripts as a complete set, preserving recovery files if publication fails.+- **Installer snapshots stay private and separate.** Configuration copies use private permissions. Rotation preserves unusual path characters, stays within the selected instance and requires ownership evidence before removing older copies.+- **Unix setup handles existing permissions.** Agent commands recognise passwordless sudo, and non-root preflight handles root-owned installer directories. Moving to the safe profile preserves the hostname already reported.+- **Agent updates match the executable version.** Checks use the installed binary's version format. Lifecycle discovery also recovers when a peer stream is cancelled.+- **Server updates finish reliably.** Helper replacement avoids truncating running scripts, and preparation failures preserve helpers. Completion avoids an unsupported API call and checks that the installed executable still matches the running service.+- **Installer downloads are bounded.** Saved installer and manual-update downloads use HTTPS through redirects and connection and download deadlines. Help explains verification before executing downloaded installers.+- **NAS upgrades preserve other startup jobs.** Unraid and QNAP updates retain unrelated boot commands and stop on unrecognised arrangements. Unraid removal refuses to affect an unrelated live boot shell.+- **Proxmox installation leaves 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.+- **Removal failures preserve recovery data.** Windows keeps files and credentials if unregistration fails, even if its service is gone, and unattended errors exit without a dialogue. Server removal retains configuration until earlier steps succeed.++## Pulse Pro, AI and hosted++- **Patrol follows the selected resource.** Alerts and findings, including demo findings, use consistent identities and group only matching problems. Open work counts, filter badges, approvals and summaries match the resource being browsed.+- **Active Docker problems stay open.** Patrol skips paid resolution reviews when current container evidence still shows the fault. Missing condition readings or healthy unrelated metrics cannot imply recovery.+- **External agents can read recent changes.** Community API and MCP tool list_recent_changes expose fleet changes with time, resource, kind and source filters. Results indicate when more changes matched than were returned.+- **External agents can read metric history.** API and MCP tool get_metric_history return recorded resource metrics under the same limits as Pulse charts, including supported Kubernetes resources.+- **Agent event streams announce more changes.** API and MCP subscribers receive alerts firing or resolving and resource status changes. Rapid status changes are grouped, with individual transitions available in history.+- **External-agent activity is counted separately.** Pulse browsing and demo reads do not count as external use. Telemetry counts days with successful agent history reads without including queries, resource IDs or results.+- **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.+- **Unread investigations offer a safe retry.** Patrol distinguishes failed history and message reads from an absent investigation, labels retained results and blocks another run until history is readable. Retry can recover failed startup reads.+- **Licence recovery reports beside its controls.** Manual recovery keeps progress and errors visible. Help distinguishes activating a licence from recovering the private runtime.+- **AI provider Help explains where data goes.** Privacy guidance describes provider processing, local endpoints and retained context, and explains that turning off usage telemetry does not stop AI requests.+- **MSP billing respects cancellation.** Plans points to Manage billing for renewal or end dates instead of promising renewal. Help 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.+- **Missing backup times stay cautionary.** Workloads says No completed backup reported rather than implying a guest has never been backed up. A running backup is no longer described as its first.+- **Incomplete guest status is rejected.** Proxmox responses missing usable status or identifying the wrong guest cannot supply readings or action checks. Healthy powered-state observations reset diagnostic alert runs.+- **Cluster startup and links are more reliable.** Duplicate clusters consolidate before monitoring and agent registration. Discovered members open their reported Proxmox address when a short hostname would not work in the browser.+- **Backup polling stops and resumes cleanly.** Expired or stopped scans cancel waiting work. Replacing a connection starts its own scan, and accepted progress survives later log timeouts.+- **Busy backup jobs share polling time.** PVE rotates unfinished log reads so live jobs stay current without starving ended jobs. Malformed task logs cannot invent guest backup results.+- **Replication failures stay visible.** Proxmox Replication distinguishes unread inventory from no jobs and offers recovery. Missing or malformed sync times stay Unknown instead of implying a successful run.+- **PBS readings preserve uncertainty.** Datastore counts stay tied to its server and datastore and distinguish unread from zero. Capacity percentages follow bytes, while memory preserves valid percentages and marks missing readings unavailable or stale.+- **Mail Gateway reports useful partial results.** Queue totals use Postfix summaries, and delay uses the oldest age band excluding held mail. Optional failures show Degraded without throttling working reads, while parsing errors stay distinct from outages.+- **Change history recognises restarts.** Uptime resets record guest, node and host restarts. Restarting Pulse avoids rediscovering the fleet and records changes after downtime without inventing their times.+- **Optional Proxmox checks back off after refusals.** Permission-denied update and guest-memory reads stop retrying every poll. Retained update counts stay stale, and a successful zero count clears the displayed old value.++## Security++- **CSV text stays text in spreadsheets.** Reports, VM inventory and audit exports prevent supplied text from becoming formulas. Audit checks and JSON exports retain original event data.+- **Tokens use current permissions.** Requests recheck live workspace tokens after configuration changes or revocation. Dashboard and agent event streams end when authority is withdrawn, and invalid explicit tokens cannot fall through to browser sessions.+- **Agent access requires appropriate permissions.** Non-admin browser and proxy users cannot submit telemetry, acknowledge Docker commands or read agent configuration containing probe credentials.+- **Monitoring reads protect execution details.** Recent changes and agent action reads hide command text, output and runbook messages unless the caller also has execution permission.+- **Oversized security inputs are bounded.** Pulse limits decompressed WebSocket messages before buffering them. Updated OIDC key and token verification libraries address security flaws and limit oversized RSA key input.+- **Administrative selections must be unambiguous.** SSO, access recovery, role checks 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 saved settings and live sign-ins.** Ordinary edits retain advanced options and secrets, while environment-managed providers keep their authority. Name, icon and ordering changes preserve sign-ins and logouts already in progress.+- **SSO tests describe their limits.** OIDC tests match the sign-in issuer, including trailing slashes, and SAML checks require an identity and usable SSO URL. Tests do not claim a completed sign-in, and provider labels retain complete characters.+- **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 identifies the separate administrator recovery path.+- **Legacy cleanup preserves recovery access.** Cleanup requires complete inventory, protects shared SSH key targets and retains recovery keys when local removal cannot finish.++## Other improvements++- **Recovery saves related data together.** Settings imports commit guest metadata with settings and credentials. Failed writes restore previous files and preserve older recovery backups.+- **Repeated imports cannot overwrite newer edits.** Concurrent imports are blocked per workspace, and recently submitted backups cannot be applied again for ten minutes.+- **Transfers stay with the confirmed workspace.** Recovery 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 errors identify components that did not reload. Uncertain responses warn that changes may already have applied and advise inspecting the destination before repeating the import.+- **Backup passphrases are independent.** Recovery exports ask users to choose and confirm a backup passphrase of at least 12 characters, rather than suggesting their sign-in password.+- **Oversized imports stop before upload.** Recovery checks file and request sizes before reading or sending oversized backups, with an error beside the transfer controls.+- **Recovery Help explains backup limits.** Guides distinguish configuration exports and installer snapshots from full data backups. Migration guidance covers isolated trials, retained storage and handing monitoring over to one server.+- **Access settings distinguish failed reads from empty lists.** API Tokens offers Retry when inventory fails. User assignments and organisation access stay tied to the current user, workspace and completed read, blocking edits based on stale permissions.+- **Unavailable inventory fails clearly.** Manual and scheduled VM inventory exports report unavailable source data instead of producing a successful empty download.+- **Setup Help explains access choices.** Agent examples keep tokens in private files. Guides separate Linux privilege profiles, observer telemetry and Proxmox access, optional guest file reads and filesystem auditing, and container SSH setup restrictions.+- **Troubleshooting covers the right checks.** Help explains backup disagreements, update failures and stalled dashboards behind proxies. The overnight guide demonstrates agent history tools, the index lists shipped guides, and missing assets return Not Found.+- **Private reporting guidance is easier to find.** Security Help explains private vulnerability reporting and credential recovery. Configuration Help identifies findings, conversations, tool results and operator notes as private data.++## Known issues++- **Guest freezes and Windows restarts are not fully resolved.** If monitoring was stopped after a guest froze, do not restart it solely to test this beta or this release. Related fixes do not establish recovery for every affected guest.+- **Affected backups still need precautions.** Stop Pulse server monitoring before a freeze-enabled backup. Keep it stopped until independent checks confirm thaw, fresh writes on every backed-up filesystem and workload liveness, regardless of an OK task.+- **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.+- **Windows disk readings can still be unavailable.** Use the existing working Machines disk view. Do not remove or reinstall agents, restart guests or force guest-agent checks just to recover Proxmox disk readings.+- **Elevated server memory remains unresolved.** Chart improvements do not establish a lower baseline. Keep the working setup and report elevated steady usage or continued growth using existing readings at comparable uptimes and workloads.+- **Previously affected hosts need caution.** If agents or Patrol were disabled after a host lockup, keep that setup. Preserve existing evidence privately, without re-enabling them, changing GPU load or altering hardware just to recreate the incident.++## 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-rc.1.md.visuals.json b/docs/releases/RELEASE_NOTES_v6.7.0-rc.1.md.visuals.jsonnew file mode 100644index 0000000000..dc2038ee88--- /dev/null+++ b/docs/releases/RELEASE_NOTES_v6.7.0-rc.1.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-rc.1.md b/docs/releases/V6_CHANGELOG_v6.7.0-rc.1.mdnew file mode 100644index 0000000000..6868bb50c2--- /dev/null+++ b/docs/releases/V6_CHANGELOG_v6.7.0-rc.1.md@@ -0,0 +1,411 @@+# Pulse v6.7.0-rc.1++This changelog describes the changes since `v6.6.0`. Stable `v6.6.0` remains the rollback target.++## Changes since v6.6.0++- End dashboard token streams when their authority is withdrawn (#3652)+- Parse numbered contract items without repeated prefix scans (#3653)+- Make private security reporting findable before deployment guidance (#3651)+- Fail fast on backend worker contract drift before CI compilation (#3650)+- Revalidate API-token authority on agent event streams (#3649)+- Keep organization access bound to the selected read (#3648)+- fix(monitoring): align rolling alert history keys (#3647)+- Distinguish container SSH warnings from enforced key setup restrictions (#3646)+- Share source-aware race build objects with backend CI (#3645)+- Do not replace audit destinations before reading their configuration (#3644)+- Keep scoped agent action reads free of execution detail (#3642)+- Cover Coverage focus ownership during sorted live updates (#3639)+- Separate identity recovery execution from fixture preparation (#3638)+- Explain why green health can accompany a stalled dashboard (#3637)+- Prevent stale registry lookups from surviving manual checks+- Supply GNU cp to macOS Linux installer fixtures (#3636)+- Distinguish provider evidence from backup job results (#3633)+- Separate installation completion from a usable Pulse server (#3632)+- Publish served agent installers as a complete bundle (#3631)+- Require whole PBS datastore discovery before reconciling backups (#3630)+- Explain where AI provider context is processed (#3629)+- Require confirmed startup before reporting server installation success (#3628)+- Capture saved-permission identity and read-state regressions (#3627)+- Reject ambiguous PBS running-writer inventories (#3626)+- Require ownership evidence before rotating configuration snapshots (#3624)+- Capture API token inventory read-state regressions (#3623)+- Require whole PBS inventory responses before reconciling history (#3622)+- Keep stored findings and operator notes private in configuration help (#3621)+- Stop installation when directory setup is incomplete (#3620)+- Keep exact reported dates inspectable in By date records (#3619)+- Bind installer help checks to byte-preserving snapshot paths (#3617)+- Keep unread PBS writer inventories from declaring failed backups (#3614)+- Explain installer configuration snapshot scope before recovery (#3613)+- Preserve trailing pathname bytes in configuration snapshots (#3612)+- Keep configuration snapshot rotation in its literal instance namespace (#3610)+- Show reported Coverage dates without hover (#3609)+- Preserve accepted PBS listings through later collection expiry (#3608)+- Explain unknown restore-point sizes without implying empty backups (#3607)+- Refuse installed executable drift during updater readback (#3606)+- Keep Coverage restore-point identifiers readable without hover (#3605)+- Balance slow backend source slices by measured runtime (#3603)+- Distinguish licence activation from private-runtime recovery (#3602)+- Keep unknown backup sizes distinct from measured bytes (#3601)+- Refresh Docker tag evidence after a local image replacement (#3596)+- Explain cached Docker update evidence before repeating an action (#3597)+- Keep manual licence recovery feedback beside its controls (#3595)+- Overlap isolated installer lifecycle validation within Go's budget (#3594)+- Keep selected PBS datastore evidence readable without hover (#3592)+- Preserve accepted storage backup evidence through later poll expiry (#3591)+- Balance complete documentation safety CI with measured suites (#3590)+- Explain PBS datastore counts without implying backup recovery (#3588)+- Keep unread PBS backup counts legible at intermediate widths (#3587)+- Avoid idle HTTP fixture teardown waits (#3586)+- Explain missing and uncertain backup task durations (#3585)+- Keep PBS backup counts with their exact reader and datastore (#3584)+- Overlap isolated installer replacement refusal controls (#3583)+- Bound waiting work in Proxmox guest snapshot polling (#3582)+- Overlap isolated memory-reader deadline controls (#3581)+- Keep unobserved backup task durations unknown (#3580)+- Make existing extra-temperature and fan readings discoverable (#3579)+- Bind background backup scans to their connection lifetime (#3578)+- Overlap isolated incident-log deadline controls (#3577)+- Keep unreadable replication sync times unknown (#3576)+- Keep source policy audits independent of runtime file churn (#3575)+- Overlap isolated passive-preflight deadline controls (#3571)+- Use a confirmed recovery passphrase for configuration exports (#3573)+- Overlap owned synthetic deadline controls (#3569)+- Make observer telemetry and Proxmox access separate choices (#3568)+- Reject malformed Proxmox task logs before guest synthesis (#3566)+- Bound configuration imports before reading and dispatching (#3567)+- Restore complete rootful installer source binding (#3564)+- Keep unread replication inventory distinct from absent jobs (#3563)+- Explain the distinct Linux agent privilege profiles (#3562)+- Rotate unfinished vzdump log reads within the existing allowance (#3561)+- Overlap private NAS removal models after live process checks (#3560)+- Keep keyboard position when backup evidence is withdrawn (#3558)+- Separate optional guest file access from filesystem auditing (#3559)+- Back off optional Proxmox permission-denied reads (#3557)+- Find native restore-point identifiers in both backup views (#3556)+- Overlap private updater discovery and recovery validators (#3555)+- Keep provider connection setup within intended trust and access (#3553)+- Identify each dated backup disclosure by its restore point (#3552)+- Explain optional Proxmox refusals without widening access (#3551)+- Explain the limits of restore-point evidence beside its state (#3550)+- Keep installer configuration snapshots private during copying (#3548)+- Keep contradictory backup task results from completing archives (#3549)+- Explain organisation access refusals in webhook setup (#3547)+- Withhold cached guest SMART readings when their scoped read fails (#3545)+- Reject PBS snapshots outside their requested group (#3543)+- Release v6.7.0-beta.3 (#3544)+- Keep backup evidence disclosure visible on phones (#3537)+- Clarify backup task-log collection in the overnight walkthrough (#3536)+- Distinguish Docker image storage from retained Pulse data (#3535)+- Test that mock mode records no history-read day (#3534)+- Reuse verified macOS Python without relinking runner tools (#3533)+- Keep backup-server memory readings faithful to their evidence (#3530)+- Bound signed installer downloads to verified HTTPS (#3531)+- Add a walkthrough for asking Pulse what happened overnight (#3526)+- Select a supported Python for native macOS contract checks (#3529)+- Bound uncertain backup task evidence on disclosure (#3527)+- Keep restarts from re-recording every resource as discovered (#3525)+- Avoid repeated server payloads in Docker image layers (#3524)+- Keep security recovery requests private and single-step (#3522)+- Keep conflicting archive subjects off guest protection (#3520)+- Bound fleet protection assessment request fan-out (#3521)+- Partition complete frontend unit proof across isolated CI shards (#3519)+- Reject ambiguous backup inventory identities (#3516)+- Refuse unsafe Docker authentication file paths in setup help (#3518)+- Preserve live SSO bindings across presentation-only edits (#3515)+- Keep test-only precompilation scoped to changed Go packages (#3514)+- Explain HTTPS-only image checks before registry login (#3513)+- Reject unread TrueNAS protection histories (#3512)+- Build the lifecycle agent once per installer test process (#3510)+- Verify saved MCP installers before executing them (#3508)+- Preserve saved access when startup discovery fails (#3509)+- Count the days external agents read Pulse history (#3507)+- Overlap isolated collector lifecycle acceptance checks (#3505)+- Make image check failures readable without hovering (#3504)+- Require explicit PBS backup inventory arrays before reconciling absence (#3502)+- Keep failed sign-in discovery distinct from first-run setup (#3501)+- Overlap independent real-agent and transport installer checks (#3500)+- Let agents read a resource's metric history (#3496)+- Keep routine PBS datastore payloads out of polling logs (#3499)+- Explain the agent-local private registry login boundary (#3497)+- Release v6.7.0-beta.3 (#3498)+- Distinguish unread investigation history from absent history (#3495)+- Record guest, node and host reboots in the change record (#3494)+- Stop counting the Pulse UI as external agent use (#3492)+- Overlap isolated guidance checks within the existing Go test budget (#3493)+- Push alert and status changes to the agent event stream (#3491)+- Keep malformed TrueNAS protection dates unknown (#3490)+- Retain observed PBS files across timeout and throttle responses (#3489)+- Let agents read what changed across the fleet (#3465)+- Keep conflicting feedback categories out of automatic triage (#3488)+- Scope dense interaction checks to their own controls (#3486)+- Keep conflicting issue-version declarations ambiguous (#3485)+- Read CORE 13 native Free and ARC from one authenticated realtime frame (#3483)+- Do not shorten malformed issue versions into release labels (#3482)+- Parse serializer test scripts as HTML (#3481)+- Keep noisy CI test diagnostics out of an output-sized heap (#3479)+- Preserve declared issue versions in loose Markdown lists (#3480)+- Keep missing workload backup evidence unknown (#3476)+- Keep secondary issue topics out of primary metadata (#3477)+- Separate cached-backup fixture polls at durable clock precision (#3474)+- Recheck issue changes between metadata removals (#3475)+- Exercise Solid's real resource serialization consumer (#3473)+- Keep future backup clocks out of verified rollup claims (#3472)+- Keep SSO endpoint values and copy controls within narrow cards (#3471)+- Explain the clocks behind backup protection assessments (#3470)+- Keep restore-point identity readable without hover (#3469)+- Release completed API capacity to the backend package queue (#3466)+- Distinguish TrueNAS disk activity and ARC composition in Help (#3464)+- Retain CORE physical-disk throughput through chart history (#3462)+- Expose the recorded clocks behind backup protection assessments (#3463)+- Keep complete benchmark pairs within isolated package shards (#3460)+- Reject damaged RBAC integrity organisation selections (#3459)+- Keep the Help index out of unshipped documentation routes (#3457)+- Keep PBS datastore fullness consistent with its used bytes (#3458)+- Release v6.7.0-beta.3 (#3456)+- Supply GNU readlink to macOS Linux installer fixtures (#3455)+- Keep snapshot recovery subjects bound to their observed guest kind (#3454)+- 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-rc.1`+- 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 requireddiff --git a/frontend-modern/public/docs/UPGRADE_v6.md b/frontend-modern/public/docs/UPGRADE_v6.mdindex ca6c789731..f78c173c5b 100644--- a/frontend-modern/public/docs/UPGRADE_v6.md+++ b/frontend-modern/public/docs/UPGRADE_v6.md@@ -7,10 +7,10 @@ Choose an actually [published software release](https://github.com/rcourtman/Pulnot a draft, source tag or Helm-chart asset. Keep the existing runtime edition:public Community downloads do not replace a private Pro build.-For the current v6 beta packet, see:+For the current v6 release candidate packet, see:-- `docs/releases/RELEASE_NOTES_v6.7.0-beta.3.md`-- `docs/releases/V6_CHANGELOG_v6.7.0-beta.3.md`+- `docs/releases/RELEASE_NOTES_v6.7.0-rc.1.md`+- `docs/releases/V6_CHANGELOG_v6.7.0-rc.1.md`For the current stable v6 packet, see:diff --git a/scripts/install-docker.sh b/scripts/install-docker.shindex 1748894800..032d7cd0c7 100755--- a/scripts/install-docker.sh+++ b/scripts/install-docker.sh@@ -6,7 +6,7 @@ set -euo pipefailSCRIPT_DIR="$(CDPATH= cd -- "$(dirname -- "$0")" && pwd)"DOCKER_IMAGE_REPO="${DOCKER_IMAGE_REPO:-rcourtman/pulse}"-CANONICAL_DEFAULT_PULSE_VERSION="6.7.0-beta.3"+CANONICAL_DEFAULT_PULSE_VERSION="6.7.0-rc.1"resolve_default_pulse_version() {if [ -n "${PULSE_IMAGE_VERSION:-}" ]; then