Sonar · Deploy log · File 47-N
What we shipped,
when, and why.
Updated in lockstep with deploys. For the operational health of what’s running right now, see status.
Feature
v5.1.0
Seven new signals — team patterns and a manager-facing mirror
The brief now watches twelve patterns instead of five. Five new ones cover team-level dynamics — pair collaboration, review quality, the invisible carrier, codebase ownership concentration, and long-running branches. Two more turn the lens back on you: response-time and 1:1 equity across your reports, and gaps between high output and acknowledgment.
- Collaboration rift — two people who used to work closely have gone silent
- Review quality — large PRs approved in under 2 minutes with no comments
- Invisible carrier — high review load + answering everyone's blockers, own output flat
- Bus factor — one person owns 85%+ of commits in a critical service
- Scope drift — long-running branch, 40+ commits, still no open PR
- Attention gap — uneven response time or 1:1 length across your reports (private to you)
- Credit gap — three weeks of high output, zero public acknowledgment
Feature
v5.0.0-rc.5
Read your morning brief in Slack
If you live in Slack, your morning brief can now arrive there as a 1:1 DM instead of (or alongside) email. Same content, same privacy posture, one fewer tab.
- Choose email, Slack DM, or both from your notification preferences
- Stop the Slack delivery any time without losing the email path
- Misconfigured workspace? You still get the brief by email automatically
Feature
v5.0.0-rc.4
Slack-first managers can run Sonar without leaving Slack
A small set of slash commands lets you pull your brief, pause collection, or check status from inside Slack. For workspace admins, feature toggles are now self-serve.
- /sonar brief · /sonar pause · /sonar status · /sonar help · /sonar unsubscribe
- Workspace admins can flip beta features on or off without filing a ticket
Feature
v5.0.0-rc.3
Resolve disputes + new in-app support form
If a teammate disputes something Sonar flagged about them, admins can now actually close the loop — accept, reject, or update with a written reason. Support questions go through a first-party form instead of a third-party widget.
- Dispute resolve / reject with a required reason, all logged
- First-party support form replaces the embedded chat widget
Milestone
v5.0.0-rc.2
GA blockers — what we shipped to be ready
Final pre-launch sweep: every public page, the cookie consent + privacy + CCPA flow, Stripe Customer Portal for self-serve billing, and the live status page. The only remaining items are external dependencies: SOC 2 Type I auditor and the next external pen test.
- Cookie consent + privacy policy + CCPA Do-Not-Sell page
- Stripe Customer Portal for self-serve plan + payment-method changes
- Live status page for API, worker, and brief delivery health
- CDN caching on the public marketing pages
Milestone
v5.0.0-rc.1
Sonar end-to-end (initial five-signal release)
First end-to-end release. Five individual signals shipped (Stalled, Gone quiet, Overloaded, Checking out, Rising) feeding the morning brief; the seven team + manager signals followed in v5.1.0 above. Trust Layer v2 (pause / opt-out / export / delete), bias monitoring, kill-switch, retention rules, billing, meeting summaries, 1:1 prep memory, public trust page.
- Five individual-level signals live, with per-org weighting (team + manager signals added in v5.1.0)
- Pause, export, and 30-day-grace delete for every employee
- Stripe billing with full subscription lifecycle
- Public trust page with subprocessor list + commitments
Last updated . RSS feed + email subscription are on the roadmap. Source of truth lives in lib/changelog/entries.ts.