Repository navigation
fix(deps): update dependency @sentry/node to v11 - #800
Open
renovate[bot] wants to merge 1 commit into
Open
renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
renovate
Bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
19 times, most recently
from
October 2, 2026 22:34
23894bd to
049f39a
Compare
renovate
Bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
10 times, most recently
from
October 6, 2026 08:52
b86ad6a to
022a7a0
Compare
renovate
Bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
22 times, most recently
from
October 17, 2026 04:53
e4cf785 to
6857613
Compare
renovate
Bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
7 times, most recently
from
October 21, 2026 02:25
b6abf09 to
daeaebb
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Note
This PR body was truncated due to platform limits.
This PR contains the following updates:
10.77.1→11.11.0Release Notes
getsentry/sentry-javascript (@sentry/node)
v11.11.0Compare Source
Important Changes
ref(cloudflare): Use the shared request handler wrapper (#25588)
Cloudflare Workers now use the same request handler wrapper as
Deno.serveandBun.serve. Changes for Cloudflare users:client.addressfrom theCF-Connecting-IPheader (or another forwarding header), as on the other runtimes. This followsdataCollection.userInfo, which istrueby default. To leave it out, setdataCollection: { userInfo: false }.responsecontext with the status code.captureErrors: false, it does not capture it.Set-Cookieheader of a response, as on Deno and Bun.AsyncLocalStorage(for example on Shopify Oxygen), events now also get the request URL and method.feat(nestjs): Add an option to monitor every @Cron method (#25471)
Set
monitorCronJobs: trueonnestIntegration()to send check-ins for every@Cron()method, without adding@SentryCronto each one. It's off by default. Each monitored job creates a monitor in Sentry, and monitors are billed. UseexcludeCronJobsto skip jobs by slug. Methods that also have@SentryCroncheck in once, with the slug and options passed to@SentryCron.feat(node): Add cronJobIntegration to monitor cron jobs (#25477)
Add
Sentry.cronJobIntegration()tointegrationsto send check-ins for every namedCronJobof thecronpackage (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. UseexcludeJobsto skip jobs by name.Sentry.cron.instrumentCronis deprecated; usecronJobIntegrationinstead.fix(server-utils): Instrument @anthropic-ai/sdk 1.x and turn off its own OTel spans (#25750)
The Anthropic integration now instruments
@anthropic-ai/sdk1.x. Since 0.134 the SDK also records its own OpenTelemetry spans, such asanthropic.messages.create, which duplicated Sentry'sgen_aispans. Once Sentry instruments the SDK, it setsANTHROPIC_OPEN_TELEMETRY=falseto turn those spans off. To keep them, setANTHROPIC_OPEN_TELEMETRY=trueor pass theopenTelemetryoption to the Anthropic client.feat(nextjs): Mark pageloads of cached pages (#25318)
When Next.js serves a page from its cache, for example an ISR page or a
cacheComponentsshell, the pageload now has thepage.server_rendering.typeattribute. It isstaticif the whole page came from the cache, andpartially_staticif parts of it rendered for this request. Then the pageload stays connected to this request, as before. If the request that rendered the cached page was sampled, the pageload also links to it. So in Sentry, a cached page no longer looks like missing server instrumentation.Other Changes
@sentry/astro/integrationentry for the Astro integration (#25726)sourcemaps.deleteSourcemapsAfterUploadand staged uploads (#25637)applicationKeyExcludeDependenciesoption (#25818)awsLambdaWebIntegrationfor Lambda Web Functions (#25355)getSqlSpanNamefor SQL span names (#25929)getSqlQueryAttributeshelper for consistency (#25927)db.operation.nameon SQL spans (#25850)withSentryfrom@sentry/solidstart/vite(#25725)handleTunnelRequestform and reword theserveTunnelIntegrationdocs (#25844)Internal Changes
canaryVariants(#25866)36c7292to01bcb7f(#25954)requiresParentSpanin favor ofonlyIfParent(#25926)canaryVariants(#25865)nuxt-5 (tunnel-dev)e2e variant optional (#26004)Work in this release was contributed by @lazerg, @chiliec, @61465, @jpdefo, and @AyeshaWaseemAhmad. Thank you for your contributions!
v11.10.0Compare Source
Important Changes
feat: Add a managed tunnel that the SDK derives from the DSN (#25199, #25200, #25783)
Set
tunnel: truein your browserSentry.initcall 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:If the browser uses a different DSN than the server, set
serveTunnelIntegration({ allowedDsns: [browserDsn] }). For other setups, the server SDKs exporthandleTunnelRequestIfMatched,handleTunnelRequest,isTunnelRequestandgetTunnelPath:The
requestoption ofhandleTunnelRequestis deprecated and will be removed in v12.feat: Make span origins spec compliant (#25602)
Some span origins changed their names to follow the trace origin spec:
auto.amqplib.*is nowauto.queue.amqplib.*, andauto.kafkajs.*is nowauto.queue.kafkajs.*.auto.vercelai.channelis nowauto.ai.vercelai.auto.firebase.firestoreis nowauto.db.firebase.firestore, andauto.firebase.functionsis nowauto.function.firebase.auto.aws.aws_sdkis nowauto.{rpc,db,queue,ai}.aws_sdk, with the category from the span op.auto.aws_lambdais nowauto.function.aws_serverless.auto.mcp.notificationis nowauto.function.mcp_server.notification.auto.db.cloudflare.durable_object.sqlis nowauto.db.cloudflare.durable_object_sql.auto.http.browser.{lcp,cls,inp}is nowauto.ui.browser.{lcp,cls,inp}.If you have
ignoreSpansrules, queries or alerts on the old origins, change them to use the new origins.feat(bun): Add incoming request options and request sessions to
bunServerIntegration(#25580)bunServerIntegrationnow accepts the same options asdenoServeIntegration:ignoreRequestBody,ignoreIncomingRequests,ignoreStaticAssets,spans,onSpanCreated,onSpanEnd,sessionsandsessionFlushingDelayMS. The callbacks receive the webRequest.Bun.servenow records a request session for each incoming request. Sessions are sent only when areleaseis set. To turn them off, setbunServerIntegration({ sessions: false }).ignoreStaticAssetsdefaults totrue, soBun.serveno longer creates spans forGETrequests to common static assets such asfavicon.ico,robots.txtor*.jsfiles. To keep these spans, setbunServerIntegration({ ignoreStaticAssets: false }).Bun.servespans also follow the client's tracing configuration by default, so the integration does not start spans when tracing is disabled. Errors thrown forOPTIONSandHEADrequests are now captured.feat(bun): Inject debug IDs and upload source maps in
sentryBunPlugin(#25670)sentryBunPluginfrom@sentry/bun/pluginnow accepts the same options assentryEsbuildPlugin(org,project,authToken,release,sourcemaps, ...). WhenBun.buildwrites source maps tooutdir, the plugin injects the debug ID that Bun writes into each bundle, injects the release, and uploads the source maps at the end of the build. You no longer need to runsentry sourcemap injectandsentry sourcemap uploadafter the build.Like the other bundler plugins,
sentryBunPluginnow sends build telemetry and injects the release it detects (for example, from git). To turn off telemetry, settelemetry: false.feat(cloudflare): Add incoming request span options to
httpServerIntegration(#25582)Cloudflare's
httpServerIntegrationnow acceptsignoreIncomingRequests,ignoreStaticAssets,spans,onSpanCreatedandonSpanEnd, with the same meaning as in the Node, Deno and Bun integrations. The callbacks receive the webRequest.ignoreStaticAssetsdefaults totrue, so workers no longer create spans forGETrequests to common static assets such asfavicon.ico,robots.txtor*.jsfiles. To keep these spans, sethttpServerIntegration({ ignoreStaticAssets: false }). Request spans also follow the client's tracing configuration by default, so the SDK does not start them when tracing is disabled. IfignoreRequestBodythrows, the request no longer fails, and the SDK skips the body.feat(cloudflare): Let users configure the channel integrations (#25584)
When the
@sentry/cloudflare/viteplugin bundles an instrumented package (for examplepgoropenai), the SDK adds the matching integration with its default options.@sentry/cloudflarenow exports these integrations, so you can set their options, for example ininstrument.server.ts:These integrations need the vite plugin. Without it, they record nothing, and with
debug: truethe SDK logs a warning.feat(node): Add
onSpanEndtohttpIntegration(#25581)httpIntegrationandhttpServerSpansIntegrationnow acceptonSpanEnd, a hook that runs when the response for an incoming request finishes, before its span ends. Use it to change the span based on the response. Deno and Bun already have this option.feat(node, bun, deno, cloudflare): Align portable exports across server SDKs (#25583)
Node, Bun, Deno and Cloudflare now export the same helpers from
@sentry/coreand@sentry/server-utilswhere they work on that runtime:moduleMetadataIntegration,instrumentPostgresJsSql,instrumentCreateReactAgent,awsIntegrationand theFlueOptionstype.awsIntegrationwas already in their default integrations.parameterizeandinstrumentStateGraphCompile.LogandLogSeverityLeveltypes.fastifyIntegration, which was already in its default integrations.feat(nuxt): Start the server SDK on the Nuxt Vite server (experimental) (#25524)
Sentry now supports Node.js production builds using Nuxt 4.6's experimental Vite server (
server: { builder: 'vite' }). Yoursentry.server.configloads automatically, enabling request tracing and automatic database spans for supported libraries.Development mode, Cloudflare, automatic capture of server rendering errors, and connecting server and browser traces via HTML meta tags are not yet supported. This experimental support may change in minor releases.
ref(deno, bun): Use a shared request handler wrapper for
Deno.serveandBun.serve(#25586, #25587)Deno.serveandBun.servenow use the same request handler wrapper, which Cloudflare will also use. On both runtimes, errors inOPTIONSandHEADrequests now carry the request data, and the SDK keeps everySet-Cookieheader of a response instead of only the last one.For Deno users:
Bun.servespans now follow the Sentry conventions forhttp.serverspans, as on Node, Deno and Cloudflare:url.templateis nowhttp.route. Routes without parameters also gethttp.routeand theroutesource.url.domainis nowserver.address./gets theroutesource and the nameGET /.user_agent.originalandhttp.request.body.size.Other Changes
execute_toolspans for Anthropic'sbeta.sessions.events.toolRunner()(#25554)varin the Vite transform (#25663)defaultkeyword in the Vite transform (#25741)undicifetch andnode:http(#25441)Internal Changes
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.