Devzy v2.10.0 Release Notes

This release centers on day-to-day visibility and control: a redesigned analytics dashboard with first-scan onboarding, and preferences that can be scoped per repository. Under the hood, the review engine is substantially smarter—whole-change investigation, stronger finding verification, and ticket-aware context—so teams get higher-signal feedback with less noise.

New Features

Redesigned Analytics Dashboard

The dashboard is rebuilt around organization health and actionable attention items, so teams can see review and compliance posture at a glance.

• Ring gauges summarize bug, compliance, and security status for the current organization scope
• A first-scan onboarding path walks newly connected repositories through their initial analysis
• Attention items surface repositories that need a first scan or follow-up action

Repository-Level Preferences

Review and automation settings can now be configured per repository, not only at the organization level.

• Admins can override organization defaults for individual repositories
• A compact preferences context bar shows the active scope and lets you switch repositories without leaving the page
• Security Review Lane settings live on their own preferences tab for clearer configuration

Ticket and Issue Context in Reviews

Pull request reviews can incorporate linked issue context so findings align with the intended change.

• Closing-issue references from pull request descriptions are injected into the review context
• Issue keys in titles and bodies are resolved when available from connected trackers
• Ticket wrapper tags are normalized before extraction to avoid noisy or incomplete context

Improvements

Investigation-Led Whole-Change Reviews

The primary review path now investigates the change as a whole, then focuses analysis by review lane with deterministic cross-file resolution.

• Lane-focused review replaces a single undifferentiated whole-change pass
• Cross-file relationships are resolved more consistently across the pull request
• Phase-level time budgets and streaming investigation clusters reduce lost findings on large changes
• Agentic context gathering helps the reviewer stay productive within those budgets

Stronger Finding Verification

An agentic verifier checks claims against evidence before comments are posted, cutting false positives and empty reviews.

• Proof-oriented verification prefers confirmed, evidence-backed findings
• Speculative and design-preference comments are more likely to be dropped
• Severity is down-rated for guarded or rarely triggered defects
• Blank or timed-out model responses retry or fall back instead of failing the entire review

Evidence-Based Compliance and Secure Coding Guidance

Compliance and secure-coding checks are more practical and evidence-oriented.

• SOC 2 and DevSecOps rules emphasize evidence-based checks rather than brittle pattern matches
• Diff review includes stronger secure-coding guidance alongside existing compliance frameworks

Preferences and Documentation Polish

• Preferences context UI behaves correctly across organization and repository scopes
• Documentation sections updated for dashboard, repositories, and related setup flows

Bug Fixes

• Fixed: Reviews stalling for long periods before recovery; stuck reviews now recover on a much shorter cycle
• Fixed: Investigation clusters silently dropped under provider timeouts
• Fixed: Unvalidated security pattern matches posting as false-positive findings

Infrastructure

• Shared data package updates across services for preferences, analytics, and connector schema compatibility
• Review workspace capacity increased to support larger repositories more reliably
• Dependency and container updates for platform stability
• CI and deploy pipeline refinements for faster, more targeted validation