## Recce v1.45.0 ### Column-Level Lineage Loads Fast on Large Projects Lineage pages on large dbt projects now load and stay responsive, and column-level lineage is available almost as soon as the instance comes up. That matters because teams with thousands of models used to hit a wall on the lineage page: a 30 MB initial lineage load, a slow first paint, and every drag or click in the CLL view compounded the cost. 🧪 In open beta. Turn it on by clicking Open Beta in Recce Cloud. Under the hood, the initial lineage load now ships only the lineage skeleton, and detailed model data and metadata are fetched on-demand when you open a model. Our cloud environment adds end-to-end compression to further reduce the data payload and serves pre-computed column-level lineage directly, so it’s ready before the instance even finishes booting. * * * ### One Share Button From OSS to Cloud There is now one clear path from an OSS session to a Cloud shared session, and a link sent to someone outside the org lands on a Request Access page instead of a blank 403. The Cloud Share button now lives in the OSS nav bar by default. When a recipient outside the org clicks a shared link, they see the Request Access page; the admin gets an email, approves or denies from a review page, and the recipient lands on the session. Invited new users are auto-accepted into the org during signup so they land directly on the shared session without a second click. * * * ### Deep Links That Make Agent PR Reviews Clickable Reviewers and PR review agents now get one click from a finding in a GitHub PR comment to the exact check detail page in Recce Cloud. Before this release, the check references the review agent produced were plain text, so confirming a finding meant switching tabs, opening Recce Cloud, and hunting for the right check. One more click between reading a finding and trusting it. v1.45.0 ships deterministic deep links. The first bold title in each bullet becomes a clickable link to the corresponding Recce Cloud check page. On the MCP side, `create_check` now auto-approves successful runs the same way `execute_preset_checks` does, keeping the checklist in sync with the actual run outcome. April 8, 2026 ## MCP Impact Analysis Verifies Downstream Data, Agent Skips Non-Data PRs ### `impact_analysis` Tool Verifies Downstream Data Changes Recce’s MCP server includes `impact_analysis`, a tool that identifies which models are affected by a PR. Previously it reported which models were downstream of a change, but couldn’t tell you whether their data actually differed. Agents had to guess which downstream models were worth investigating. Now `impact_analysis` runs row-level comparison on downstream table models and reports whether each one has confirmed data changes, no changes, or needs manual verification. In eval testing, this lifted agent detection accuracy from 87% to 100% when paired with updated reviewer prompts. * * * ### Recce Agent Skips Non-Data PRs PRs that don’t touch data models were still triggering full Recce analysis — producing reports about “schema changes” that existed before the PR. The Recce Agent now detects non-data PRs and skips the analysis call entirely. No wasted agent runs, no false-positive noise in PR reviews. * * * ### Axios Removed After Supply-Chain Compromise The [Axios v1.14.1 npm package was compromised with a RAT](https://www.aikido.dev/blog/axios-npm-compromised-maintainer-hijacked-rat). Recce was never running the compromised version, but we removed the dependency entirely — both OSS and Cloud — replacing it with a thin native `fetch` wrapper. 67+ source files migrated across both repositories, zero Axios imports remain. One fewer supply-chain surface to worry about. April 1, 2026 ## Track Every Recce Data Review Run with Checklist Status in Your PR ### Track Every Recce Data Review Run Directly in Your PR Recce Data Review results in PR comments previously had no per-check status or run attribution. Reviewers could not tell which checks passed or failed at a glance, or trace a result back to a specific run. PR comments now show a structured checklist where each check displays its status — Passed, Failed, Analyzed, or Pending. Each item links to the full run history in Recce Cloud. The Activity panel tracks every run with attribution (user or AI), giving teams a complete audit trail across CI cycles. * * * ### Fewer False Positives in Recce Data Review Recce Data Review sometimes flagged schema or lineage changes that had no actual data impact, creating noise for reviewers who then learned to ignore findings. The analysis prompt now includes guardrails that filter out changes unlikely to affect data. Reviewers see fewer irrelevant findings, which keeps the signal-to-noise ratio high and maintains trust in Recce Data Review. * * * ### Faster CLI Startup Running any `recce` command incurred a multi-second delay because the CLI loaded all dependencies at startup, even for simple operations like `recce version`. Commands that do not require the full stack now start significantly faster, which reduces friction in scripted workflows and CI pipelines. * * * ### Lineage Viewport Fits Large Graphs on Load Opening a lineage diff for a large project showed the entire graph at maximum zoom-out, making individual nodes too small to read. Users had to manually zoom and pan to find the relevant area. The initial viewport now calculates a zoom level that keeps nodes legible while showing the most relevant portion of the graph. Large projects are readable on first load without manual adjustment. * * * ### Exports Go Beyond the Preview Limit Exporting query results was capped at the 2,000-row preview limit, which truncated large datasets and forced workarounds. Exports are no longer capped at the 2,000-row preview limit — CSV and TSV support up to 500K rows, and Excel up to 100K. Download buttons show the total row count, and large exports trigger a confirmation dialog before starting. * * * ### Python 3.9 Support Dropped Recce no longer supports Python 3.9, which reached end-of-life in October 2025. If you are still on Python 3.9, upgrade to Python 3.10 or later before updating Recce.