Sentry

New opt-in cronTriggersIntegration sends check-ins for Cloudflare Cron Triggers, and a new neonIntegration creates db spans for @neondatabase/serverless, on by default when tracing is enabled. Node servers no longer send a duplicate process session once request sessions are tracked, and gen_ai.evaluate spans are renamed gen_ai.decide.

Deprecates send_default_pii and transaction profiling, and adds sentry.is_localhost plus user_agent.original attributes for inbound filters across ASGI, WSGI, aiohttp, Sanic, and Tornado. Also fixes request-body scrubbing for JSON arrays and Boto3 StreamingBody span handling.

The SDK now captures native crashes such as segmentation faults as minidumps and sends them to Sentry on Linux, macOS, and Windows, covering crashes in unsafe code and FFI calls into C libraries that occur without a panic. Enabled by compiling the sentry crate with the minidump feature and adding MinidumpIntegration at init.

Sentry.init() now warns when it runs while a client is still active, and Sentry.close() unbinds the client it closes so getClient() returns undefined and isInitialized() returns false afterward. Also deprecated SEMANTIC_ATTRIBUTE_SENTRY_ORIGIN and removed the beforeSendSpan null return warning.

The first curated Scraps entries are published for themes, tokens, layout, typography, separators, quotes, loaders, inline code, and keyboard key labels.

Fixes NS_ERROR_NOT_INITIALIZED from setTimeout in Firefox, includes basePath in Pages Router request URLs for Next.js, and stops injecting debug IDs into Nuxt SSR builds. Also corrects overlapping feedback screenshot annotations, shares one root render span debounce timer across Vue components, and exports consoleLoggingIntegration from the SvelteKit worker entry.

Sentry now integrates with Origin, providing stack trace linking that jumps from a stack frame to the exact line in Origin, CODEOWNERS import for email-based ownership rules, release commit tracking, and issue resolution via fix references in commit messages and PR descriptions. Connecting one Origin account to multiple Sentry organizations requires a Business or Enterprise plan.

@sentry/node and @sentry/bun now include dedupeIntegration in their default integrations, so when the same error is captured twice in a row only the first event is sent. Hono is now instrumented automatically with request spans named after matched routes, plus fixes for Express layer spans, buffered metric flushing on Deno and Node, and raw Anthropic, Groq, Together, and OpenAI response body preservation.

The hosted Sentry MCP server can now create, update, and delete alert rules and metric monitors, and a new link_issue tool attaches Jira, GitHub, GitLab, Bitbucket, Azure DevOps, or Sentry App tickets and GitHub pull requests to Sentry issues by URL. Writes require the Manage Projects & Teams skill, and existing connections must re-authorize to grant the new alerts:write OAuth scope.

Seer Agent can now write to Sentry through the Sentry API, setting up custom dashboards and widgets, creating monitors and alerts, assigning, resolving, and archiving issues, and saving explore queries and issue views, using the user's existing permissions with write-scope confirmation per action. Seer Connectors also pull infrastructure data from Datadog and Google Cloud Platform via API keys, not OAuth, alongside Sentry data.

Fixed Next.js middleware tunnel request matching to align with the tunnel rewrite. Internal changes cover AWS layer version templating and e2e test fixes.

The Python SDK now traces TypeSafe Jev calls.