You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
feat(metrics): Add top level option enableMetrics and beforeSendMetric (#18088)
This PR moves enableMetrics and beforeSendMetric out of the _experiments options.
The metrics feature will now be enabled by default (none of our integrations will auto-emit metrics as of now), but you can disable sending metrics via enableMetrics: false.
Metric options within _experiments got deprecated but will still work as of now, they will be removed with the next major version of our SDKs.
Other Changes
feat(aws): Add SENTRY_LAYER_EXTENSION to configure using the lambda layer extension via env variables (#18101)
feat(core): Include all exception object keys instead of truncating (#18044)
feat(node): Instrument cloud functions for firebase v2 (#17952)
We added instrumentation for Cloud Functions for Firebase v2, enabling automatic performance tracking and error monitoring. This will be added automatically if you have enabled tracing.
feat(browserProfiling): Add trace lifecycle mode for UI profiling (#17619)
Adds a new trace lifecycle mode for UI profiling, allowing profiles to be captured for the duration of a trace. A manual mode will be added in a future release.
Adds a new Growthbook integration for feature flag support.
feat(solid): Add support for TanStack Router Solid (#17735)
Adds support for TanStack Router in the Solid SDK, enabling better routing instrumentation for Solid applications.
feat(nextjs): Support native debugIds in turbopack (#17853)
Adds support for native Debug IDs in Turbopack, improving source map resolution and error tracking for Next.js applications using Turbopack. Native Debug ID generation will be enabled automatically for compatible versions.
Other Changes
feat(nextjs): Prepare for next 16 bundler default (#17868)
feat(nuxt): Implement server middleware instrumentation (#17796)
This release introduces instrumentation for Nuxt middleware, ensuring that all middleware handlers are automatically wrapped with tracing and error reporting functionality.
fix(aws-serverless): Take http_proxy into account when choosing useLayerExtension default (#17817)
The default setting for useLayerExtension now considers the http_proxy environment variable.
When http_proxy is set, useLayerExtension will be off by default.
If you use a http_proxy but would still like to make use of the Sentry Lambda extension, exempt localhost in a no_proxy environment variable.
Other Changes
feat(node): Split up http integration into composable parts (#17524)
fix(core): Remove check and always respect ai.telemetry.functionId for Vercel AI gen spans (#17811)
doc(core): Fix outdated JSDoc in beforeSendSpan (#17815)
Internal Changes
ci: Do not run dependabot on e2e test applications (#17813)
docs: Reword changelog for google gen ai integration (#17805)
feat(cloudflare): Add honoIntegration with error-filtering function (#17743)
This release adds a honoIntegration to @sentry/cloudflare, which exposes a shouldHandleError function that lets you define which errors in onError should be captured.
By default, Sentry captures exceptions with error.status >= 500 || error.status <= 299.
The integration is added by default, and it's possible to modify this behavior like this:
integrations: [honoIntegration({shouldHandleError: (err)=>true;// always capture exceptions in onError})]
feat(node): Add instrumentation for hono handler (#17428)
This PR enhances the Hono integration by adding comprehensive handler instrumentation, error handling capabilities.
feat(aws): Enable Lambda extension by default when using the Lamba layer (#17684)
feat(browser): Add setActiveSpanInBrowser to set an active span in the browser (#17714)
This PR adds a feature to the browser SDKs only: Making an inactive span active. We do this to enable use cases where having a span only being active in the callback is not practical.
Other Changes
fix(browser): Improve handling of 0 and undefined resource timing values (#17751)
ref(nextjs): Display build compatibility warning for webpack (#17746)
Internal Changes
docs: Reword changelog for google gen ai instrumentation (#17753)
feat(cloudflare,vercel-edge): Add support for Google Gen AI instrumentation (#17723)
The SDK now supports manually instrumenting Google's Gen AI operations in Cloudflare Workers and Vercel Edge Runtime environments, providing insights into your AI operations. You can use const wrappedClient = Sentry.instrumentGoogleGenAIClient(genAiClient) to get an instrumented client.
feat(browser): Add option to explicitly end pageload span via reportPageLoaded() (#17697)
With this release you can take manual control of ending the pageload span. Usually this span is ended automatically by the SDK, based on a period of inactivity after the initial page was loaded in the browser. If you want full control over the pageload duration, you can tell Sentry, when your page was fully loaded:
Sentry.init({//...integrations: [// 1. Enable manual pageload reportingSentry.browserTracingIntegration({enableReportPageLoaded: true}),],});// 2. Whenever you decide the page is loaded, call:Sentry.reportPageLoaded();
Note that if Sentry.reportPageLoaded() is not called within 30 seconds of the initial pageload (or whatever value the finalTimeout option is set to), the pageload span will be ended automatically.
feat(core,node): Add instrumentation for GoogleGenAI (#17625)
The SDK now automatically instruments the @google/genai package to provide insights into your AI operations.
feat(nextjs): Promote useRunAfterProductionCompileHook to non-experimental build option (#17721)
The useRunAfterProductionCompileHook option is no longer experimental and is now a stable build option for Next.js projects.
feat(nextjs): Use afterProductionCompile hook for webpack builds (#17655)
Next.js projects using webpack can opt-in to use the useRunAfterProductionCompileHook hook for source map uploads.
feat(nextjs): Flip default value for useRunAfterProductionCompileHook for Turbopack builds (#17722)
The useRunAfterProductionCompileHook option is now enabled by default for Turbopack builds, enabling automated source map uploads.
feat(node): Do not drop 300 and 304 status codes by default (#17686)
HTTP transactions with 300 and 304 status codes are now captured by default, providing better visibility into redirect and caching behavior.
Other Changes
feat(core): Add logger to core and allow scope to be passed log methods (#17698)
feat(core): Allow to pass onSuccess to handleCallbackErrors (#17679)
feat(core): Create template attributes in consoleLoggingIntegration (#17703)
This release includes a variety of changes aimed at setting the mechanism field on errors captured automatically by the Sentry SDKs. The intention is to clearly mark which instrumentation captured an error. In addition, some instrumentations previously did not yet annotate the error as handled or unhandled which this series of PRs corrects as well.
ref(deno): Adjust mechanism of errors caught by globalHandlersIntegration (#17635)
ref(nextjs): Set more specific event mechanisms (#17543)
ref(node): Adjust mechanism of express, hapi and fastify error handlers (#17623)
ref(node-core): Add mechanism to cron instrumentations (#17544)
ref(node-core): Add more specific mechanism.type to worker thread errors from childProcessIntegration (#17578)
ref(node-core): Adjust mechanism of onUnhandledRejection and onUnhandledException integrations (#17636)
ref(node): Add mechanism to errors captured via connect and koa integrations (#17579)
ref(nuxt): Add and adjust mechanism.type in error events (#17599)
ref(react): Add mechanism to reactErrorHandler and adjust mechanism in ErrorBoundary (#17602)
ref(remix): Adjust event mechanism of captureRemixServerException (#17629)
ref(replay-internal): Add mechanism to error caught by replayIntegration in debug mode (#17606)
ref(solid): Add mechanism to error captured by withSentryErrorBoundary (#17607)
ref(solidstart): Adjust event mechanism in withServerActionInstrumentation (#17637)
ref(sveltekit): Adjust mechanism of error events (#17646)
ref(vue): Adjust mechanism in Vue error handler (#17647)
Released in 10.11.0:
ref(browser): Add more specific mechanism.type to errors captured by httpClientIntegration (#17254)
ref(browser): Set more descriptive mechanism.type in browserApiErrorsIntergation (#17251)
ref(core): Add mechanism.type to trpcMiddleware errors (#17287)
ref(core): Add more specific event mechanisms and span origins to openAiIntegration (#17288)
ref(nestjs): Add mechanism to captured errors (#17312)
feat(node) Ensure prismaIntegration works with Prisma 5 (#17595)
We used to require to pass in the v5 version of @prisma/instrumentation into prismaIntegration({ prismaInstrumentation: new PrismaInstrumentation() }), if you wanted to get full instrumentation for Prisma v5. However, it turns out this does not work on v10 of the SDK anymore, because @prisma/instrumentation@5 requires OTEL v1.
With this release, we dropped the requirement to configure anything to get v5 support of Prisma. You do not need to configure anything in the integration anymore, and can remove the dependency on @prisma/instrumentation@5 if you had it in your application. You only need to configure the tracing preview feature according to our docs.
feat(aws): Add experimental AWS Lambda extension for tunnelling events (#17525)
This release adds an experimental Sentry Lambda extension to the existing Sentry Lambda layer. Sentry events are now tunneled through the extension and then forwarded to Sentry. This has the benefit of reducing the request processing time.
To enable it, set _experiments.enableLambdaExtension in your Sentry config like this:
feat(browser): Add support for propagateTraceparent SDK option (#17509)
Adds support for a new browser SDK init option, propagateTraceparent for attaching a W3C compliant traceparent header to outgoing fetch and XHR requests, in addition to sentry-trace and baggage headers. More details can be found here.
feat(core): Add tool calls attributes for Anthropic AI (#17478)
Adds missing tool call attributes, we add gen_ai.response.tool_calls attribute for Anthropic AI, supporting both streaming and non-streaming requests.
feat(nextjs): Use compiler hook for uploading turbopack sourcemaps (#17352)
Adds a new experimental flag _experimental.useRunAfterProductionCompileHook to `withSent
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
If you want to rebase/retry this PR, check this box
Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.
♻ Renovate will retry this branch, including artifacts, only when one of the following happens:
any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually
The artifact failure details are included below:
File name: front/package-lock.json
npm warn Unknown env config "store". This will stop working in the next major version of npm.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @welldone-software/[email protected]
npm error Found: [email protected]
npm error node_modules/react
npm error react@"~19.2.0" from the root project
npm error peer react@"^16.8.0 || ^17.0.0 || ^18.0.0 || ^19.0.0" from @monaco-editor/[email protected]
npm error node_modules/@monaco-editor/react
npm error @monaco-editor/react@"~4.7.0" from the root project
npm error 15 more (@rjsf/core, @rjsf/utils, @testing-library/react, ...)
npm error
npm error Could not resolve dependency:
npm error peer react@"^18" from @welldone-software/[email protected]
npm error node_modules/@welldone-software/why-did-you-render
npm error dev @welldone-software/why-did-you-render@"~8.0" from the root project
npm error
npm error Conflicting peer dependency: [email protected]
npm error node_modules/react
npm error peer react@"^18" from @welldone-software/[email protected]
npm error node_modules/@welldone-software/why-did-you-render
npm error dev @welldone-software/why-did-you-render@"~8.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2025-10-28T02_44_09_118Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2025-10-28T02_44_09_118Z-debug-0.log
Il faut aussi bump @welldone-software/why-did-you-render en version 10.0 afin d'être compatible avec React 19. @thom4parisot J'ai l'impression qu'on a beaucoup moins de soucis de performance/rerender maintenant que les composants sont mieux découpés et avec l'utilisation des hooks + SWR. Peut être qu'on pourrait se passer de @welldone-software/why-did-you-render?
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.
This PR contains the following updates:
^8.38.0->^10.0.0^4.3.4->^5.0.0~18.3->~19.2.0~18.3->~19.2.0Release Notes
getsentry/sentry-javascript (@sentry/react)
v10.25.0Compare Source
maxCacheKeyLengthto Redis integration (remove truncation) (#18045)Internal Changes
v10.24.0Compare Source
Important Changes
feat(metrics): Add top level option
enableMetricsandbeforeSendMetric(#18088)This PR moves
enableMetricsandbeforeSendMetricout of the_experimentsoptions.The metrics feature will now be enabled by default (none of our integrations will auto-emit metrics as of now), but you can disable sending metrics via
enableMetrics: false.Metric options within
_experimentsgot deprecated but will still work as of now, they will be removed with the next major version of our SDKs.Other Changes
SENTRY_LAYER_EXTENSIONto configure using the lambda layer extension via env variables (#18101)background-imagewhenblockAllMediais enabled (#18019)Internal Changes
v10.23.0Compare Source
user-agentheader with envelope requests in server SDKs (#17929)maxValueLength: 250(#18043)optionsparameter optional onattachErrorHandler(#18072)internal_errorinstead ofunknown_error(#17909)Internal Changes
Work in this release was contributed by @hanseo0507. Thank you for your contribution!
v10.22.0Compare Source
Important Changes
feat(node): Instrument cloud functions for firebase v2 (#17952)
We added instrumentation for Cloud Functions for Firebase v2, enabling automatic performance tracking and error monitoring. This will be added automatically if you have enabled tracing.
feat(core): Instrument LangChain AI (#17955)
Instrumentation was added for LangChain AI operations. You can configure what is recorded like this:
Other Changes
err(#17999)/when getting pathname (#17985)spanEndfor potentially cancelled lazy-route transactions (#17962)Internal Changes
getMetaTagTransformertests for Vitest compatibility (#18013)createHashRouter(#17789)v10.21.0Compare Source
Important Changes
feat(browserProfiling): Add
tracelifecycle mode for UI profiling (#17619)Adds a new
tracelifecycle mode for UI profiling, allowing profiles to be captured for the duration of a trace. Amanualmode will be added in a future release.feat(nuxt): Instrument Database (#17899)
Adds instrumentation for Nuxt database operations, enabling better performance tracking of database queries.
feat(nuxt): Instrument server cache API (#17886)
Adds instrumentation for Nuxt's server cache API, providing visibility into cache operations.
feat(nuxt): Instrument storage API (#17858)
Adds instrumentation for Nuxt's storage API, enabling tracking of storage operations.
Other Changes
onRequestSpanEndhook to browser tracing integration (#17884)clean-css(#17979)Internal Changes
Work in this release was contributed by @0xbad0c0d3. Thank you for your contribution!
v10.20.0Compare Source
Important Changes
feat(flags): Add Growthbook integration (#17440)
Adds a new Growthbook integration for feature flag support.
feat(solid): Add support for TanStack Router Solid (#17735)
Adds support for TanStack Router in the Solid SDK, enabling better routing instrumentation for Solid applications.
feat(nextjs): Support native debugIds in turbopack (#17853)
Adds support for native Debug IDs in Turbopack, improving source map resolution and error tracking for Next.js applications using Turbopack. Native Debug ID generation will be enabled automatically for compatible versions.
Other Changes
pinologger name (#17930)POPguard for long-runningpageloadspans (#17867)Internal Changes
- chore(nextjs): Add Next.js 16 peer dependency ([#17925](https://github.com/getsentry/sentry-javascript/pull/17925)) - chore(ci): Update Next.js canary testing ([#17939](https://github.com/getsentry/sentry-javascript/pull/17939)) - chore: Bump size limit ([#17941](https://github.com/getsentry/sentry-javascript/pull/17941)) - test(nextjs): Add next@16 e2e test ([#17922](https://github.com/getsentry/sentry-javascript/pull/17922)) - test(nextjs): Update next 15 tests ([#17919](https://github.com/getsentry/sentry-javascript/pull/17919)) - chore: Add external contributor to CHANGELOG.md ([#17915](https://github.com/getsentry/sentry-javascript/pull/17915)) - chore: Add external contributor to CHANGELOG.md ([#17928](https://github.com/getsentry/sentry-javascript/pull/17928)) - chore: Add external contributor to CHANGELOG.md ([#17940](https://github.com/getsentry/sentry-javascript/pull/17940))Work in this release was contributed by @seoyeon9888, @madhuchavva and @thedanchez. Thank you for your contributions!
v10.19.0Compare Source
Internal Changes
v10.18.0Compare Source
Important Changes
feat(node):
pinointegration (#17584)This release adds a new
pinointegration for Node.js, enabling Sentry to capture logs from the Pino logging library.feat: Remove @sentry/pino-transport package (#17851)
The
@sentry/pino-transportpackage has been removed. Please use the newpinointegration in@sentry/nodeinstead.feat(node-core): Extend onnhandledrejection with ignore errors option (#17736)
Added support for selectively suppressing specific errors with configurable logging control in onnhandledrejection integration.
Other Changes
sentry.client.config.tsin nuxt app types (#17830)OriginalHandleRequestwith middleware (#17870)Internal Changes
Work in this release was contributed by @stefanvanderwolf. Thank you for your contribution!
v10.17.0Compare Source
Important Changes
feat(nuxt): Implement server middleware instrumentation (#17796)
This release introduces instrumentation for Nuxt middleware, ensuring that all middleware handlers are automatically wrapped with tracing and error reporting functionality.
fix(aws-serverless): Take
http_proxyinto account when choosinguseLayerExtensiondefault (#17817)The default setting for
useLayerExtensionnow considers thehttp_proxyenvironment variable.When
http_proxyis set,useLayerExtensionwill be off by default.If you use a
http_proxybut would still like to make use of the Sentry Lambda extension, exemptlocalhostin ano_proxyenvironment variable.Other Changes
beforeSendSpan(#17815)Internal Changes
v10.16.0Compare Source
replay_is_bufferingflag (#17752)instrumentAnthropicAiClientbreaking MessageStream api (#17754)Internal Changes
publish_releasecommand (#17797)import-in-the-middlewhen building the Lambda layer (#17780)[email protected]due to@vercel/nftincompatibility (#17777)" (#17784)[email protected]due to@vercel/nftincompatibility (#17777)v10.15.0Compare Source
Important Changes
feat(cloudflare): Add honoIntegration with error-filtering function (#17743)
This release adds a
honoIntegrationto@sentry/cloudflare, which exposes ashouldHandleErrorfunction that lets you define which errors inonErrorshould be captured.By default, Sentry captures exceptions with
error.status >= 500 || error.status <= 299.The integration is added by default, and it's possible to modify this behavior like this:
feat(node): Add instrumentation for hono handler (#17428)
This PR enhances the Hono integration by adding comprehensive handler instrumentation, error handling capabilities.
feat(aws): Enable Lambda extension by default when using the Lamba layer (#17684)
feat(browser): Add
setActiveSpanInBrowserto set an active span in the browser (#17714)This PR adds a feature to the browser SDKs only: Making an inactive span active. We do this to enable use cases where having a span only being active in the callback is not practical.
Other Changes
0andundefinedresource timing values (#17751)Internal Changes
@typescript-eslint/no-unnecessary-type-assertionrule (#17728)es2020everywhere (#17709)Work in this release was contributed by @Karibash. Thank you for your contribution!
v10.14.0Compare Source
Important Changes
feat(cloudflare,vercel-edge): Add support for Google Gen AI instrumentation (#17723)
The SDK now supports manually instrumenting Google's Gen AI operations in Cloudflare Workers and Vercel Edge Runtime environments, providing insights into your AI operations. You can use
const wrappedClient = Sentry.instrumentGoogleGenAIClient(genAiClient)to get an instrumented client.Other Changes
WeakRefwhen storing it on spans (#17712)Internal Changes
v10.13.0Compare Source
Important Changes
feat(browser): Add option to explicitly end pageload span via
reportPageLoaded()(#17697)With this release you can take manual control of ending the pageload span. Usually this span is ended automatically by the SDK, based on a period of inactivity after the initial page was loaded in the browser. If you want full control over the pageload duration, you can tell Sentry, when your page was fully loaded:
Note that if
Sentry.reportPageLoaded()is not called within 30 seconds of the initial pageload (or whatever value thefinalTimeoutoption is set to), the pageload span will be ended automatically.feat(core,node): Add instrumentation for
GoogleGenAI(#17625)The SDK now automatically instruments the
@google/genaipackage to provide insights into your AI operations.feat(nextjs): Promote
useRunAfterProductionCompileHookto non-experimental build option (#17721)The
useRunAfterProductionCompileHookoption is no longer experimental and is now a stable build option for Next.js projects.feat(nextjs): Use
afterProductionCompilehook for webpack builds (#17655)Next.js projects using webpack can opt-in to use the
useRunAfterProductionCompileHookhook for source map uploads.feat(nextjs): Flip default value for
useRunAfterProductionCompileHookfor Turbopack builds (#17722)The
useRunAfterProductionCompileHookoption is now enabled by default for Turbopack builds, enabling automated source map uploads.feat(node): Do not drop 300 and 304 status codes by default (#17686)
HTTP transactions with 300 and 304 status codes are now captured by default, providing better visibility into redirect and caching behavior.
Other Changes
onSuccesstohandleCallbackErrors(#17679)consoleLoggingIntegration(#17703)oscontext (#17720)thirdPartyErrorFilterIntegration(#17693)thiscontext for vercel AI instrumentation (#17681)Internal Changes
reportPageLoaded(#17724)getTestMatrix(#17673)SyncPromisewhere not needed (#17641)ignoreSpans(#17692)module_metadataassignment and cleanup functions (#17696)HandleDocumentRequestFunction(#17680)Work in this release was contributed by @Olexandr88. Thank you for your contribution!
v10.12.0Compare Source
Important Changes
ref: Add and Adjust error event
mechanismvaluesThis release includes a variety of changes aimed at setting the
mechanismfield on errors captured automatically by the Sentry SDKs. The intention is to clearly mark which instrumentation captured an error. In addition, some instrumentations previously did not yet annotate the error as handled or unhandled which this series of PRs corrects as well.Relevant PRs
Released in
10.12.0:mechanismon error events captured by astro middleware (#17613)mechanismof errors captured in Bun.serve (#17616)mechanismsand durable object origin (#17618)mechanismincaptureConsoleIntegration(#17633)mechanism(#17622)linkedErrorsmechanism logic (#17600)mechanismof errors caught byglobalHandlersIntegration(#17635)mechanisms (#17543)mechanismto cron instrumentations (#17544)mechanism.typeto worker thread errors fromchildProcessIntegration(#17578)mechanismofonUnhandledRejectionandonUnhandledExceptionintegrations (#17636)mechanism.typein error events (#17599)reactErrorHandlerand adjust mechanism inErrorBoundary(#17602)captureRemixServerException(#17629)replayIntegrationin debug mode (#17606)mechanismto error captured bywithSentryErrorBoundary(#17607)mechanismof error events (#17646)Released in
10.11.0:mechanism.typeto errors captured byhttpClientIntegration(#17254)mechanism.typeinbrowserApiErrorsIntergation(#17251)mechanism.typetotrpcMiddlewareerrors (#17287)mechanisms and span origins toopenAiIntegration(#17288)mechanismto captured errors (#17312)prismaIntegrationworks with Prisma 5 (#17595)We used to require to pass in the v5 version of
@prisma/instrumentationintoprismaIntegration({ prismaInstrumentation: new PrismaInstrumentation() }), if you wanted to get full instrumentation for Prisma v5. However, it turns out this does not work on v10 of the SDK anymore, because@prisma/instrumentation@5requires OTEL v1.With this release, we dropped the requirement to configure anything to get v5 support of Prisma. You do not need to configure anything in the integration anymore, and can remove the dependency on
@prisma/instrumentation@5if you had it in your application. You only need to configure thetracingpreview feature according to our docs.Other Changes
TracesSamplerSamplingContexttype (#17523)prismaIntegrationworks with Prisma v5 (#17595)parentSpanIdstays consistent during trace in TwP mode (#17526)step.do(#17582)_platformproperties in Nitro 2.11.7+ (#17596)shimmer(#17597) - ref(nuxt): Add and adjustmechanism.typein error events (#17599)fetchTransporterror handling (#17661)Internal Changes
.claude/settings.local.jsonto.claude/settings.json(#17591)flushIfServerlesstest (#17610)v10.11.0Compare Source
Important Changes
feat(aws): Add experimental AWS Lambda extension for tunnelling events (#17525)
This release adds an experimental Sentry Lambda extension to the existing Sentry Lambda layer. Sentry events are now tunneled through the extension and then forwarded to Sentry. This has the benefit of reducing the request processing time.
To enable it, set
_experiments.enableLambdaExtensionin your Sentry config like this:Other Changes
handleExistingNavigation(#17534)mechanism.typeto errors captured byhttpClientIntegration(#17254)mechanism.typeinbrowserApiErrorsIntergation(#17251)mechanism.typetotrpcMiddlewareerrors (#17287)mechanisms and span origins toopenAiIntegration(#17288)mechanismto captured errors (#17312)Internal Changes
test-utilsdependency in workspace (#17538)geistfont (#17541)v10.10.0Compare Source
Important Changes
propagateTraceparentSDK option (#17509)Adds support for a new browser SDK init option,
propagateTraceparentfor attaching a W3C compliant traceparent header to outgoing fetch and XHR requests, in addition to sentry-trace and baggage headers. More details can be found here.Adds missing tool call attributes, we add gen_ai.response.tool_calls attribute for Anthropic AI, supporting both streaming and non-streaming requests.
Adds a new experimental flag
_experimental.useRunAfterProductionCompileHookto `withSentConfiguration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Renovate Bot.