mirror of
https://github.com/rcourtman/Pulse.git
synced 2026-10-24 12:42:49 +00:00
pulse-triage[bot]
b052d29b19
## What changed and why Reduce configuration-fetch audit overhead without hiding access events (#2320). The suppression tracker now remembers at most 4,096 organisation/agent pairs and uses an expiry index instead of repeated full-map scans. Existing agents keep daily suppression; unremembered agents at capacity are conservatively audited on every fetch. Token/configuration changes and every failure remain audited. No audit history is deleted. The Apprise confidentiality test now observes the autonomous queue dispatcher instead of starting a competing manual batch. Its lifecycle, retry, configuration and confidentiality assertions remain intact. Preserve the exact 6.4.6 release-line mapping for the already-published packet. The fallback to main incorrectly rejected its immutable source during convergence. This maps that version only, not future patches, and changes no candidate product source. ## Included source and upstream reconciliation Complete new publication range: `e6540da45da4de4bcb954463373d8ea9f196eb56..35d8c7c13d3665b2ffe2fe4fd61e8952c46e21b1`. - Reviewed Delivery correction: `3578b0044740087e7589f19bca450245f610aced`. - Reviewed Core changes: `e225bf2abcb4189dcedd457292248e72a945dc74` and `6ab5383412f156f286c38623f9b86f2b0d3151f0`, integrated by `94ce8496b7d79e9b77d43493adc432c954d5e8b7`. - Additive upstream merge: `35d8c7c13d3665b2ffe2fe4fd61e8952c46e21b1`, incorporating published Proxmox table repairs at `e6540da45da4de4bcb954463373d8ea9f196eb56`. Every reviewed commit identity and ancestry is preserved. No upstream frontend source or dependency manifest changes in this proposal. ## Validation and limits Recorded independent-review evidence: Core returned four complete source-proof receipts covering connected configuration-fetch/authorization tests, five race repeats, notifications correctness/races and ten queue-fixture repeats, vet/builds, 135 governance tests, 23 docs-sync tests and frontend production build/budgets. Its fixed controls retained a maximum of 4,096 keys versus 12,288 in the predecessor; saturated in-memory lookup measurements are not installed write-rate or CPU acceptance. Delivery returned a complete offline source proof of 947 release-control tests (8 skipped), with guest shutdown. The exact-version tests reject unrelated versions. These are reviewed owner returns, not new qualification executions by this publication gate. On the combined committed source, provenance, whitespace, ancestry, canonical completion, browser-verification scope, control-plane audit, all 62 shipped-document mirrors and the 211-file public-document check pass. Core runtime and Go manifests are byte-identical to the reviewed Core candidate; release-control source/policy is byte-identical to the reviewed Delivery candidate; frontend runtime and graph are byte-identical to current upstream. Sufficient heavy/browser evidence was therefore not replayed. Core used Go 1.26.7 rather than declared 1.26.8, with an explicit backend embed fixture and a separately proved frontend build. Required exact-head CI remains necessary before landing. This proposal does not establish installed outcomes, release readiness, successful convergence or stable delivery, and does not replace or recut the published v6.4.6 candidate. [How Pulse handles triage](https://github.com/rcourtman/Pulse/blob/main/docs/AI_TRANSPARENCY.md)
Pulse documentation
Start here for installation, platform setup, security, operations, and Pulse Intelligence. Commands, configuration keys, image names, API fields, and product identifiers remain untranslated in localized guides.
Start here
- Install Pulse — signed Proxmox/Linux installation, Docker, Docker Compose, Kubernetes, and first-run setup.
- Production deployment and security — least-privilege Proxmox setup, root-agent boundaries, discovery, supply-chain verification, plan limits, scale evidence, and a rollout checklist.
- Upgrade from Pulse v5 — migration prerequisites, rollback, agent continuity, and post-upgrade checks.
- Releases and update channels: choosing Stable or Preview, beta and RC expectations, and how releases are tested and promoted.
- Configure Pulse — authentication, notifications, discovery, retention, and system settings.
- Deployment models — data locations, lifecycle, and differences between supported deployment paths.
- Troubleshooting and FAQ — common failures, diagnostics, and operator questions.
Localized getting started guides: Deutsch · Español
Platforms and agents
- Proxmox Backup Server
- Proxmox Mail Gateway
- Docker and Podman
- Kubernetes and Helm
- TrueNAS SCALE and CORE
- Unified Agent
- Agent security
- VM disk monitoring
- ZFS monitoring
- Temperature monitoring
VMware vSphere support is early access. Current builds expose dedicated vSphere inventory and recovery context, but operators should validate the integration against their own vCenter before production use.
Monitoring and operations
- Metrics history
- Recovery data
- Webhooks
- Automatic updates
- Centralized agent management (Pro)
- Operational trust model
- Current product screenshots
Pulse Intelligence
- Assistant, Patrol, and external-agent overview
- Patrol modes and safety
- Assistant safety model
- External agent HTTP and MCP substrate
Patrol watch-only analysis is available on Community with a local model or the operator's own provider. Investigation and governed fixes require the relevant Pulse Pro capabilities.
Security, privacy, and access
- Production deployment and security
- Security review scope
- Authentication and credential storage review packet
- Security guide
- Privacy and telemetry disclosure
- OIDC and SSO
- Proxy authentication
- Role-based access control (Pro)
- Audit logging (Pro)
- Reverse proxy configuration
- Code-signing policy
Plans and managed access
- Community, Relay, and Pro capabilities
- Relay and Pulse Mobile handoff
- Multi-tenant organizations (Enterprise/custom)
- Provider-hosted MSP operations (request-assisted)
Pulse Cloud is not generally available. Ordinary self-hosted Pulse remains the primary installation path; MSP and Enterprise access are explicit commercial paths rather than defaults in self-hosted setup.
Development and reference
Detailed design notes and dated migration specifications may remain in this directory for maintainers, but they are not operator setup guides unless they are linked from the sections above.
Previous versions and migrations
- Upgrade from v4 to v5
- Retired unified-navigation migration — historical context only; current Pulse uses platform-shaped navigation.
- Move a Pulse installation
Found a bug? Use the issue forms. For setup questions, use GitHub Discussions.