The React Native SDK now records the calls, duration, and errors of native modules, and adds the active call to crash reports.

The Android SDK can now instrument Nav3 back stacks to capture navigation transactions, breadcrumbs, screen names, and more.

The Rust SDK can now report native crashes, such as segfaults in unsafe code, to Sentry.

Sentry Logs search now supports regular expressions (regex), so that you can search log lines that match a pattern, not just by the exact text.

The JavaScript SDKs now trace more AI frameworks, providers, and classifiers across Node.js, Bun, Cloudflare, and Deno, with more consistent data in traces.

The Android SDK can now report process deaths caused by Android 17's Memory Limiter as fatal Sentry events.

Connect code hosted in Origin to Sentry

Agents using Sentry MCP can now create, edit, and delete Alerts and Metric Monitors, link external tickets to issues, and see the suspect commit in issue details.

Seer agent just got a lot more powerful. Now you can have the agent manage more of your Sentry projects for you and integrate third-party data sources, like Datadog and Google Cloud Platform, to help you better diagnose issues.

The JavaScript SDKs now trace TypeSafe Jev calls.

No action is needed for most users. In this release, Sentry’s published internal JavaScript packages moved from @sentry-internal/* to @sentry/*, and the SDK now depends on the new package names automatically.

A regression in data scrubbing prevented specific attributes from being scrubbed

Replay filters (events, tags, URLs, CSS selectors, etc.) can now be saved and reused later.

We’ve made a few changes to make replays easier to use and share.

Replay summaries, now available for early adopter let you quickly understand what happened in user sessions without having to watch the entire replay. Each summary provides a clear narrative and structured chapters, allowing you to jump straight to important moments and debug faster.

We've updated Sentry Docs to better reflect the Event fields we apply data scrubbing by default when using our Require Using Default Scrubbers feature.

The tree compare tool helps diagnose hydration errors in React by identifying and time stamping DOM mutations, with detailed context for debugging.

See the differences between client-rendered and server-rendered HTML when hydration occurs on your app to debug the problem faster and improve your site's web performance.

Replay now has Web Vital breadcrumbs, which show the Web Vital score as well as the elements contributing to that score.

Actionable hydration errors based on replay data are now available for early adopters.