Packages

@sentry/core

11.11.0 · 5 Nov 2026MIT101.6M / weekRepositoryHomepagenpmAtom feed

Your version

Where each line stands

Plan an upgrade

Latest releases

All 581 releases
  1. 11.x · latest line
  2. 11.11.0

    5 Nov 2026
    • Deprecated

      core: Deprecate the released handleTunnelRequest form and reword the serveTunnelIntegration docs

    • nestjs: Add an option to monitor every @Cron method

      Set monitorCronJobs: true on nestIntegration() to send check-ins for every @Cron() method, without adding @SentryCron to each one. It's off by default. Each monitored job creates a monitor in Sentry, and monitors are billed. Use excludeCronJobs to skip jobs by slug. Methods that also have @SentryCron check in once, with the slug and options passed to @SentryCron.

    • node: Add cronJobIntegration to monitor cron jobs

      Add Sentry.cronJobIntegration() to integrations to send check-ins for every named CronJob of the cron package (4.3+), with the job name as the monitor slug. It's off by default. Each monitored job creates a monitor in Sentry, and monitors are billed. Use excludeJobs to skip jobs by name. Sentry.cron.instrumentCron is deprecated; use cronJobIntegration instead.

  3. 11.10.0

    28 Oct 2026
    • Add a managed tunnel that the SDK derives from the DSN (#25199, #25200, #25783)

      Set tunnel: true in your browser Sentry.init call to send events through your own server. This helps when ad blockers block requests to Sentry. The browser derives the tunnel path from the DSN, so older and newer builds of your client and server always agree on the path.

      To serve the tunnel, add serveTunnelIntegration() to your server SDK. Astro, Nuxt, Nitro, React Router, Remix 3, SolidStart, SvelteKit and TanStack Start then answer tunnel requests automatically:

      // browser
      Sentry.init({ dsn, tunnel: true });
      
      // server
      Sentry.init({ dsn, integrations: [Sentry.serveTunnelIntegration()] });

      If the browser uses a different DSN than the server, set serveTunnelIntegration({ allowedDsns: [browserDsn] }). For other setups, the server SDKs export handleTunnelRequestIfMatched, handleTunnelRequest, isTunnelRequest and getTunnelPath:

      app.use((req, res, next) => Sentry.handleTunnelRequestIfMatched(req, res) ?? next());

      The request option of handleTunnelRequest is deprecated and will be removed in v12.

    • Make span origins spec compliant

      Some span origins changed their names to follow the trace origin spec:

      If you have ignoreSpans rules, queries or alerts on the old origins, change them to use the new origins.

    • bun: Add incoming request options and request sessions to bunServerIntegration

      bunServerIntegration now accepts the same options as denoServeIntegration: ignoreRequestBody, ignoreIncomingRequests, ignoreStaticAssets, spans, onSpanCreated, onSpanEnd, sessions and sessionFlushingDelayMS. The callbacks receive the web Request.

      Bun.serve now records a request session for each incoming request. Sessions are sent only when a release is set. To turn them off, set bunServerIntegration({ sessions: false }).

      ignoreStaticAssets defaults to true, so Bun.serve no longer creates spans for GET requests to common static assets such as favicon.ico, robots.txt or *.js files. To keep these spans, set bunServerIntegration({ ignoreStaticAssets: false }). Bun.serve spans also follow the client's tracing configuration by default, so the integration does not start spans when tracing is disabled. Errors thrown for OPTIONS and HEAD requests are now captured.

  4. 11.9.0

    22 Oct 2026
    • Rename diagnostic_channel, fetch and gRPC span origins

      Some span origins changed their names to match the other v11 origins:

      If you have ignoreSpans rules, queries or alerts on the old origins, change them to use the new origins.

    • deno: Add incoming request options to denoServeIntegration

      denoServeIntegration now accepts ignoreRequestBody, ignoreIncomingRequests, ignoreStaticAssets, spans, onSpanCreated and onSpanEnd, with the same meaning as in denoHttpIntegration. The callbacks receive the web Request.

      ignoreStaticAssets defaults to true, so Deno.serve no longer creates spans for GET requests to common static assets such as favicon.ico, robots.txt or *.js files. To keep these spans, set denoServeIntegration({ ignoreStaticAssets: false }). Deno.serve spans also follow the client's tracing configuration by default, so the integration does not start spans when tracing is disabled.

    • deno: Record request sessions for Deno.serve

      denoServeIntegration now records a request session for each incoming request, as denoHttpIntegration does for node:http. This gives release health and crash-free rates for Deno.serve apps. Sessions are sent only when a release is set. To turn them off, set denoServeIntegration({ sessions: false }). sessionFlushingDelayMS sets how long the SDK waits before it sends the session aggregate.

Dependency tracking · free for 3 projects

Know when your own dependencies move

@sentry/core shipped a new major in the last 12 months, among 78 releases. inlinr shows which of your projects are behind, and what the upgrade breaks.

  • Advisories reach you

    An email when a critical or high advisory affects a project, before the next install.

  • Upgrades checked first

    Peer ranges, Node, ESM-only and types changes read before you bump.

  • Only what matters

    Majors and breaking notes stay; patches and sibling bumps fold into one line.

How dependency tracking works

Registry facts last checked 9 Nov 2026. Releases and advisories last read 9 Nov 2026.