Repository navigation
chore(deps): update JavaScript SDK to v11.15.0 - #6773
github-actions[bot] wants to merge 1 commit into
Conversation
Semver Impact of This PR⚪ None (no version bump detected) 📋 Changelog PreviewThis is how your changes will appear in the changelog.
🤖 This preview updates automatically when you update the PR. |
antonis
left a comment
There was a problem hiding this comment.
Marking as blocked since we will bump with our next major
|
Tested out the changes with #6730 |
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 3 potential issues.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit adfb87a. Configure here.
| "@sentry/core": "11.0.0", | ||
| "@sentry/expo-upload-sourcemaps": "workspace:*", | ||
| "@sentry/react": "10.75.2" | ||
| "@sentry/react": "11.0.0" |
There was a problem hiding this comment.
PII collected by default after v11
High Severity
Flagged because the review rules require PII to stay gated behind sendDefaultPii and require changelog review on JS dependency bumps. v11 replaces sendDefaultPii with dataCollection and collects user info, cookies, HTTP bodies, and similar data by default. This SDK still documents and implements sendDefaultPii (default off) and omits dataCollection from ReactNativeOptions, so JS-core collection turns on while apps cannot disable it through the public options type.
Triggered by project rule: PR Review Guidelines for Cursor Bot
Reviewed by Cursor Bugbot for commit adfb87a. Configure here.
| "@sentry/core": "11.0.0", | ||
| "@sentry/expo-upload-sourcemaps": "workspace:*", | ||
| "@sentry/react": "10.75.2" | ||
| "@sentry/react": "11.0.0" |
There was a problem hiding this comment.
Unmigrated v11 breaking JS APIs
High Severity
Flagged because the review rules require JS dependency bumps to be checked for breaking API and default-integration changes. This PR only retargets @sentry/core, @sentry/browser, and @sentry/react to 11.0.0. Default integrations still call removed inboundFiltersIntegration, the public entry still re-exports removed instrumentLangGraph and AI helpers that moved off @sentry/core, and tracing still imports startIdleSpan from the default @sentry/core entry. No code, types, or changelog migration accompanies the major bump.
Triggered by project rule: PR Review Guidelines for Cursor Bot
Reviewed by Cursor Bugbot for commit adfb87a. Configure here.
| "@sentry/core": "11.0.0", | ||
| "@sentry/expo-upload-sourcemaps": "workspace:*", | ||
| "@sentry/react": "10.75.2" | ||
| "@sentry/react": "11.0.0" |
There was a problem hiding this comment.
Span streaming default breaks tracing
High Severity
Flagged because the review rules call out silent default and telemetry-shape changes on dependency updates. v11 enables span streaming by default and deprecates transaction-mode hooks such as beforeSendTransaction and forceTransaction. This SDK's navigation, app-start, and idle-span pipeline still assumes root spans are buffered as transactions and discarded via transaction event processors. Streaming would emit child spans before those filters run and change the telemetry apps currently receive.
Triggered by project rule: PR Review Guidelines for Cursor Bot
Reviewed by Cursor Bugbot for commit adfb87a. Configure here.
5b99eba to
a7da763
Compare
a5d19b4 to
5949ab3
Compare
9caf113 to
c8c3cc3
Compare
c2a203e to
c6bdd9e
Compare
8949646 to
b314359
Compare
e91ca5a to
4de25fc
Compare
849c853 to
255295a
Compare
14e4413 to
605c605
Compare
605c605 to
7ac8dcd
Compare
|
Any news? |
|
@sentry/react-native 8.31.0 still installs two Sentry CLIs: @sentry/[email protected] directly and @sentry/[email protected] through @sentry/[email protected]. Updating to bundler-plugins 11.x would remove the old one. Is there a date for this? |
Thanks for flagging this @mahnunchik 🙇 We have planned this for our next major v9 since the major JS SDK bump also includes breaking changes. This is planned for early 2027 since the React Native SDKs has many dependencies (including https://github.com/getsentry/sentry-cocoa and https://github.com/getsentry/sentry-java) and needs to align all in the next major. Until then the two CLIs are installed side by side and don't conflict. It only costs some extra install size. Sorry for the inconvenience. |


Bumps scripts/update-javascript.sh from 10.78.0 to 11.15.0.
Auto-generated by a dependency updater.
Changelog
11.15.0
Important Changes
feat(core): Continue MCP server traces from
params._meta(#26308)MCP server spans now continue the caller's trace from the
sentry-traceandbaggagekeys in a request's or notification'sparams._meta, so they connect to the agent that called the tool, including over stdio. SetpropagateTraceparent: trueto also continue from a W3Ctraceparentkey. On Streamable HTTP, the MCP span is no longer a child of thehttp.serverspan when the client sends trace context in_meta. It has a span link to that span instead. Messages without valid trace context in_meta, or with trace context from another Sentry org, still join the transport's trace.ref(tanstackstart-react): Use
code.file.pathon server function spans (#26495)Server function spans now set the file of the server function in
code.file.pathinstead oftanstackstart.function.filename. Thetanstackstart.function.idattribute is removed.Other Changes
sentry-releasemeta tag (#26514)bun runon Bun 1.4.6 and later (#26515)sourcemaps.upload,injectDebugIdsanddelete(#26571)resolveReleaseName(#26500)sourcemaps.upload,injectDebugIdsanddeleteto the shared build options (#26576)sourcemaps.upload,injectDebugIdsanddelete(#26606)release.inject: 'html'to keep chunk hashes stable (#26511)release.inject: 'html'to keep chunk hashes stable (#26512)bun run(#26622)release.inject: false(#26509)Internal Changes
release.inject(#26499)Work in this release was contributed by psang39. Thank you for your contribution!
11.14.0
Important Changes
feat(browser): Add
browserTracingCoreIntegrationand standalone tracing integrations (#26259, #26260, #26261, #26262, #26273, #26276, #26497)browserTracingIntegrationnow sets up fetch and XHR request spans, linked traces, long tasks and resource spans through the standalonefetchTracingIntegration,xhrTracingIntegration,linkedTracesIntegration,longTasksIntegrationandresourcesIntegration. Its behavior is unchanged. To ship less code, usebrowserTracingCoreIntegration, which keeps pageload and navigation spans, and add only the standalone integrations you need. The CDN bundles export them too.ref(server-utils): Share one cron converter across cron integrations (#25918)
Sentry.cron.instrumentCron,instrumentNodeCronandinstrumentNodeSchedulesend the server's time zone when a job has none, so monitors don't report false misses on servers that aren't on UTC. Schedules Sentry can't express exactly, such as per-second schedules, send no monitor config, so the monitor keeps the schedule set in Sentry.Sentry.cron.instrumentNodeCronis deprecated; usenodeCronIntegrationinstead.fix(nuxt): Name the database system in
db.system.nameof db0 spans (#26285)Nitro database (db0) spans now set
db.system.nameto the database system of the connector's dialect (mysql,postgresql,sqliteorlibsql), as the OpenTelemetry conventions define it, instead of the connector name. For example, spans of themysql2andplanetscaleconnectors now reportmysql, and spans ofbetter-sqlite3andcloudflare-d1now reportsqlite. Update saved queries, alerts and dashboards that filter on the connector names.Other Changes
cacheClientoption (#26494)JSON.stringifyoutput that goes into generated code (#26314)Internal Changes
Work in this release was contributed by JavierCane. Thank you for your contribution!
11.13.0
Important Changes
feat(sveltekit): Mark pageloads of prerendered and Vercel ISR pages (#26301, #26307)
When SvelteKit serves a page that it rendered earlier, the pageload now has the
page.server_rendering.type: staticattribute. This covers pages prerendered duringvite buildand pages that Vercel caches with ISR (config.isr). For an ISR page, the pageload also links to the request that rendered the page, if that request was sampled.Before, every visitor of a cached ISR page continued the trace of that one request. Now each pageload starts its own trace. Pages with
ssr = falseget no attribute, because the server rendered none of their content.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.fix(core): Set
url.schemewithout colon andurl.portas a number (#26284)HTTP spans that the SDK builds from a
URLnow sendurl.schemewithout the trailing colon (httpsinstead ofhttps:) andurl.portas a number instead of a string, as the Sentry conventions define them and as Nodehttp.serverspans already do. This changeshttp.serverspans fromsentry/cloudflare,Bun.serve, Deno and Nitro, and outgoingnode:httpclient spans. Update saved queries, alerts and dashboards that filter onurl.scheme:"https:"or onurl.portas a string.feat(cloudflare): Continue the Cloudflare trace of the invocation (#25613)
When tracing is not set up (no
tracesSampleRateortracesSampler), errors and logs from fetch, scheduled, queue and email handlers and fromWorkerEntrypointRPC methods now get the trace id that Cloudflare gives the invocation. With this trace id, you can find the Cloudflare spans and logs of an error in Workers Observability. This needs workerd 1.20261009.1 or newer and Workers Observability turned on. An incoming Sentry trace still has precedence.The
parent_span_idof these events is the id of a Cloudflare span. This span is in Sentry only when you export your Workers traces to Sentry.feat(server-utils): Record Bedrock prompts and responses (#26249, #26362, #26414)
Amazon Bedrock spans from
awsIntegrationnow record prompts, system instructions, tool definitions and responses by default, as the other AI integrations do. This applies to theConverse,ConverseStream,InvokeModelandInvokeModelWithResponseStreamcommands.To stop recording prompts or responses for all AI integrations, set
dataCollection: { genAI: { inputs: false, outputs: false } }. To stop it only for Bedrock, use the newawsIntegrationoptions, which take precedence overdataCollection.genAI:Other Changes
deleteSourcemapsAfterUpload: truewhen no upload runs (#26281)traceandtailStreamhandlers (#26250)getTraceServerTimingHeaderandisSharedCacheable(#26325)Server-Timingheader of document responses (#26107)sentry/nodestartup time (#25968)BrowserClientconstructor (#26313)application/x-sentry-envelope(#26299)urlto sentry.io (#26252)flue/runtimeprovide its own namespace (#25935)_enhanceErrorWithSentryInfo(#26349)Internal Changes
sentry/conventionsto 0.33.0 (#26374)node-abort-controllerdeprecation in the lockfile (#26270)enableLongAnimationFramedefault in JSDoc (#26256)Work in this release was contributed by kunal649, bardrop, DomWane, Vivek1898, mvanhorn, and pcbeingused333. Thank you for your contributions!
11.12.0
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)