Repository navigation
Update dependency @sentry/cloudflare to v11 - #899
Open
devdogs-renovate[bot] wants to merge 1 commit into
Open
devdogs-renovate[bot] wants to merge 1 commit into
devdogs-renovate[bot] wants to merge 1 commit into
Conversation
devdogs-renovate
Bot
requested review from
SidhantDash and
kquakk
as code owners
October 27, 2026 06:55
devdogs-renovate
Bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
from
October 31, 2026 19:27
1298cd4 to
2ad97b6
Compare
devdogs-renovate
Bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
from
November 8, 2026 18:02
2ad97b6 to
1a3e870
Compare
devdogs-renovate
Bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
from
November 13, 2026 19:54
1a3e870 to
b5160aa
Compare
This branch has not been deployed
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.75.1→11.12.0Release Notes
getsentry/sentry-javascript (@sentry/cloudflare)
v11.12.0Compare Source
Important Changes
feat(nuxt): Mark pageloads of cached pages (#26305)
When Nuxt serves a cached or prerendered page, for example with a
swrorisrroute rule, the pageload now has thepage.server_rendering.type: staticattribute and starts its own trace. If the request that rendered the cached page was sampled, the pageload also links to it. So visitors of a cached page no longer continue the trace of the request that rendered it.feat(bundler-plugins): Enable hidden source maps and remove them after upload (#25637, #25645, #25646, #25647, #25648)
The Sentry Rollup, Vite, webpack and esbuild plugins now turn on hidden source maps when your bundler has no source maps enabled and the plugin can upload them. They upload the maps to Sentry and remove them from the build output. You no longer need to set
sourcemap: 'hidden'orfilesToDeleteAfterUploadglobs:The new
sourcemaps.deleteSourcemapsAfterUploadoption controls the removal:true: the plugin also removes source maps you enabled yourself, and switches visible source maps to hidden. Set this if you already usesourcemap: 'hidden'and want to drop yourfilesToDeleteAfterUploadglobs.false: the plugin never removes source maps.Builds in development mode or without an auth token, org and project do not change.
feat(cloudflare): Propagate tracing context through Queue messages (#25306)
Cloudflare Queue consumers can now link to the traces of the producers that sent the messages. Set
queueTracePropagationBindingsto the producer bindings that should add trace data to plain-object message bodies. Consumers remove this data before your handler runs, and thequeue.processspan links to every producer in the batch.feat(core): Answer managed tunnel requests in the runtime (#25997, #25998, #25999, #26000, #26001)
serveTunnelIntegration()now answers tunnel requests before they reach your app, in Node.js, Bun, Deno, Cloudflare Workers and AWS Lambda. You no longer need a framework integration or a route handler, so any server setup works with only the integration:To answer tunnel requests from your own code, set
serveTunnelIntegration({ intercept: false })and callhandleTunnelRequestIfMatched.Other Changes
tunnelRoute(#26225)//paths inurl.full(#26165)Internal Changes
@sentry/conventionsto 0.31.0 (#26160)@sentry/conventionsto 0.32.0 (#26222)node:fsfor removal scripts (#26219)sourcemaps.assetsandsourcemaps.ignore(#25916)Work in this release was contributed by @lazerg, @rjmcgee53192, @adityankale190895, @arthurfiorette, @chan-mai, @nuntz, and @43081j. Thank you for your contributions!
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 receiConfiguration
📅 Schedule: (in timezone America/New_York)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate CLI.