Update dependency @sentry/react to v11.14.0 #525
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "renovate/sentry-javascript-monorepo"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This MR contains the following updates:
11.12.0→11.14.0Release Notes
getsentry/sentry-javascript (@sentry/react)
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
@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!
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Enabled.
♻ Rebasing: Whenever MR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this MR and you won't be reminded about this update again.
This MR has been generated by Mend Renovate CLI.
mentioned in issue #1
aborted the automatic merge because the source branch was updated. Learn more.
added 4 commits
masterCompare with previous version
changed title from
Update dependency @sentry/react to v11.13.0toUpdate dependency @sentry/react to v11.14.0changed the description
added 2 commits
343ba6f5- 1 commit from branchmasterCompare with previous version
changed the description
aborted the automatic merge because the source branch was updated. Learn more.
added 2 commits
e7f86f46- 1 commit from branchmasterCompare with previous version
added 3 commits
masterCompare with previous version
aborted the automatic merge because the source branch was updated. Learn more.
added 3 commits
masterCompare with previous version
added 3 commits
masterCompare with previous version
aborted the automatic merge because the source branch was updated. Learn more.
added 4 commits
mastereddc5338- Update dependency @sentry/react to v11.14.0Compare with previous version
eddc5338e0tod9ec8842f3View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.