Repository navigation
Update dependency @sentry/tanstackstart-react to v11 - #574
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
|
The latest updates on your projects. Learn more about Vercel for GitHub. 3 Skipped Deployments
|
renovate
Bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
3 times, most recently
from
October 1, 2026 15:02
d243512 to
fcf8d8b
Compare
renovate
Bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
7 times, most recently
from
October 7, 2026 11:28
d422262 to
c699c02
Compare
renovate
Bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
3 times, most recently
from
October 15, 2026 11:07
ec24e1e to
f6a25bd
Compare
renovate
Bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
5 times, most recently
from
October 26, 2026 23:33
eab38b9 to
ae8d397
Compare
renovate
Bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
3 times, most recently
from
October 29, 2026 22:52
6efb008 to
5f664a7
Compare
renovate
Bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
4 times, most recently
from
November 11, 2026 05:48
f182934 to
82d88b9
Compare
renovate
Bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
3 times, most recently
from
November 19, 2026 18:09
b9a7dea to
a717cb5
Compare
renovate
Bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
from
November 20, 2026 17:11
a717cb5 to
58957e8
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.78.0→11.16.0Release Notes
getsentry/sentry-javascript (@sentry/tanstackstart-react)
v11.16.0Compare Source
Important Changes
docs(tanstackstart-react): Promote SDK status to stable (#26691)
This release promotes the
@sentry/tanstackstart-reactSDK to stable. It supports@tanstack/react-start1.169.0 and newer. For details on how to use it, check out theSentry TanStack Start SDK docs.
feat(solid): Add Solid 2 support (alpha)
@sentry/solidnow ships alpha support for Solid 2 under the@sentry/solid/solid2entry point. It captures errors on the client and the server, traces navigations with Solid Router 2 via@sentry/solid/solid2/solidrouter, names server spans after the matched route, and continues the server trace in the browser pageload. The Solid 1 entry points are unchanged. The APIs of the Solid 2 entry may still change in minor releases while it is in alpha.Related PRs: #26543, #26589, #26627, #26634, #26690
Other Changes
httpIntegrationincoming-request options tonode:httpservers (#26611)Internal Changes
v11.15.0Compare Source
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!
v11.14.0Compare Source
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
01bcb7fto6bf4a27(#26447)Work in this release was contributed by @JavierCane. Thank you for your contribution!
v11.13.0Compare Source
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 from@sentry/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
Configuration
📅 Schedule: (UTC)
🚦 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 was generated by Mend Renovate. View the repository job log.