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
A new viewHierarchyIntegration captures the DOM structure when an error occurs, providing a snapshot of the page state for debugging. Enable it in your Sentry configuration:
feat(cloudflare): Split alarms into multiple traces and link them (#19373)
Durable Object alarms now create separate traces for each alarm invocation, with proper linking between related alarms for better observability.
feat(cloudflare): Enable RPC trace propagation with enableRpcTracePropagation (#19991, #20345)
A new enableRpcTracePropagation option enables automatic trace propagation for Cloudflare RPC calls via .fetch(), ensuring distributed traces flow correctly across service bindings.
All AI integrations (OpenAI, Anthropic, Google GenAI, LangChain, LangGraph) now support an enableTruncation option to control whether large AI inputs/outputs are truncated.
feat(aws-serverless): Ship Lambda extension in npm package for container image Lambdas (#20133)
The Sentry Lambda extension is now included in the npm package, enabling container image-based Lambda functions to use it. Copy the extension files into your Docker image and set the tunnel option:
RUN mkdir -p /opt/sentry-extension
COPY node_modules/@​sentry/aws-serverless/build/lambda-extension/sentry-extension /opt/extensions/sentry-extension
COPY node_modules/@​sentry/aws-serverless/build/lambda-extension/index.mjs /opt/sentry-extension/index.mjs
RUN chmod +x /opt/extensions/sentry-extension /opt/sentry-extension/index.mjs
ref(core): Unify .do* span ops to gen_ai.generate_content (#20074)
All Vercel AI do* spans (ai.generateText.doGenerate, ai.streamText.doStream, ai.generateObject.doGenerate, ai.streamObject.doStream) now use a single unified span op gen_ai.generate_content instead of separate ops like gen_ai.generate_text, gen_ai.stream_text, gen_ai.generate_object, and gen_ai.stream_object.
ref(core): Remove provider-specific AI span attributes in favor of gen_ai attributes in sentry conventions (#20011)
The following provider-specific span attributes have been removed from the OpenAI and Anthropic AI integrations. Use the standardized gen_ai.* equivalents instead:
Removed attribute
Replacement
openai.response.id
gen_ai.response.id
openai.response.model
gen_ai.response.model
openai.usage.prompt_tokens
gen_ai.usage.input_tokens
openai.usage.completion_tokens
gen_ai.usage.output_tokens
openai.response.timestamp
(removed, no replacement)
anthropic.response.timestamp
(removed, no replacement)
If you reference these attributes in hooks (e.g. beforeSendTransaction), update them to the gen_ai.* equivalents.
feat(core): Support embeddings in LangChain (#20017)
Adds instrumentation for LangChain embeddings (embedQuery, embedDocuments), creating gen_ai.embeddings spans. In Node.js, embedding classes from @langchain/openai, @langchain/google-genai, @langchain/mistralai, and @langchain/google-vertexai are auto-instrumented. For other runtimes, use the new instrumentLangChainEmbeddings API:
feat(node-core): Add OTLP integration for node-core/light (#19729)
Added otlpIntegration at @sentry/node-core/light/otlp for users who manage
their own OpenTelemetry setup and want to send trace data to Sentry without
adopting the full @sentry/node SDK.
import{NodeTracerProvider}from'@​opentelemetry/sdk-trace-node';import*asSentryfrom'@​sentry/node-core/light';import{otlpIntegration}from'@​sentry/node-core/light/otlp';constprovider=newNodeTracerProvider();provider.register();Sentry.init({dsn: '__DSN__',integrations: [otlpIntegration({// Export OTel spans to Sentry via OTLP (default: true)setupOtlpTracesExporter: true,}),],});
The integration links Sentry errors to OTel traces and exports spans to Sentry via OTLP.
feat(node, bun): Add runtime metrics integrations for Node.js and Bun (#19923, #19979)
New nodeRuntimeMetricsIntegration and bunRuntimeMetricsIntegration automatically collect runtime health metrics and send them to Sentry on a configurable interval (default: 30s). Collected metrics include memory (RSS, heap used/total), CPU utilization, event loop utilization, and process uptime. Node additionally collects event loop delay percentiles (p50, p99). Extra metrics like CPU time and external memory are available as opt-in.
feat(core): Support embedding APIs in google-genai (#19797)
Adds instrumentation for the Google GenAI embedContent API, creating gen_ai.embeddings spans.
feat(browser): Add elementTimingIntegration for tracking element render and load times (#19869)
The new elementTimingIntegration captures Element Timing API data as Sentry metrics. It emits element_timing.render_time and element_timing.load_time distribution metrics for elements annotated with the elementtiming HTML attribute.
test(astro): Re-enable server island tracing e2e test in Astro 6 (#19872)
test(cloudflare): Enable multi-worker tests for CF integration tests (#19938)
Work in this release was contributed by @roli-lpci. Thank you for your contributions!
Important Changes
feat(node): Add nodeRuntimeMetricsIntegration for automatic Node.js runtime metrics (#19923)
The new nodeRuntimeMetricsIntegration automatically collects Node.js runtime health metrics and sends them to Sentry. Eight metrics are emitted by default every 30 seconds: memory (RSS, heap used/total), CPU utilization, event loop delay (p50, p99), event loop utilization, and process uptime. Additional metrics are available as opt-in.
feat(remix): Server Timing Headers Trace Propagation (#18653)
The Remix SDK now supports automatic trace propagation via Server-Timing response headers to continue pageload traces on the client side.
This means, you no longer have to define a custom meta function to add Sentry <meta> tags to your page as previously.
We'll update out Remix tracing docs after this release.
Other Changes
fix(cloudflare): Use correct env types for withSentry (#19836)
fix(core): Align error span status message with core SpanStatusType for langchain/google-genai (#19863)
fix(deno): Clear pre-existing OTel global before registering TracerProvider (#19723)
fix(nextjs): Skip tracing for tunnel requests (#19861)
fix(node-core): Recycle propagationContext for each request (#19835)
ref(core): Simplify core utility functions for smaller bundle (#19854)
Internal Changes
chore(deps): bump next from 16.1.5 to 16.1.7 in /dev-packages/e2e-tests/test-applications/nextjs-16 (#19851)
ci(release): Switch from action-prepare-release to Craft (#18763)
This release introduces @sentry/effect, a new SDK for Effect.ts applications. The SDK provides Sentry integration via composable Effect layers for both Node.js and browser environments.
Compose the effectLayer with optional tracing, logging, and metrics layers to instrument your Effect application:
Alpha features are still in progress, may have bugs and might include breaking changes. Please reach out on GitHub if you have any feedback or concerns.
This release enables full support for Astro v6 by adjusting our Astro SDK's middleware to some Astro-internal
changes. We cannot yet guarantee full support for server-islands, due to a bug in Astro v6
but we'll follow up on this once the bug is fixed.
feat(hono): Add basic instrumentation for Node runtime (#19817)
Adds a new package @sentry/hono/node (alpha) with basic instrumentation for Hono applications running in Node.js.
The Hono middleware for Cloudflare (@sentry/hono/cloudflare - alpha) comes with fixes, and it's now possible to access the Cloudflare Worker Bindings (env) from the options' callback.
Start using the new Hono middlewares by installing @sentry/hono and importing the respective middleware for your runtime.
More instructions can be found in the Hono readme.
Alpha features are still in progress, may have bugs and might include breaking changes. Please reach out on GitHub if you have any feedback or concerns.
Automatically capture exceptions and create transactions for BullMQ queue processors in NestJS applications.
When using the @Processor decorator from @nestjs/bullmq, the SDK now automatically wraps the process() method
to create queue.process transactions with proper isolation scopes, preventing breadcrumb and scope leakage between
jobs and HTTP requests. Errors thrown in processors are captured with the auto.queue.nestjs.bullmq mechanism type.
Automatically capture exceptions thrown in @Cron, @Interval, and @Timeout decorated methods.
Previously, exceptions in @Cron methods were only captured if you used the SentryCron decorator. Now they are
captured automatically. The exception mechanism type changed from auto.cron.nestjs.async to auto.function.nestjs.cron. If you have Sentry queries or alerts that filter on the old mechanism type, update them
accordingly.
feat(node): Expose headersToSpanAttributes option on nativeNodeFetchIntegration() (#19770)
Response headers like http.response.header.content-length were previously captured automatically on outgoing
fetch spans but are now opt-in since @opentelemetry/instrumentation-undici@0.22.0. You can now configure which
headers to capture via the headersToSpanAttributes option.
feat(nextjs): Add Turbopack support for React component name annotation (#19604)
We added experimental support for React component name annotation in Turbopack builds. When enabled, JSX elements
are annotated with data-sentry-component, data-sentry-element, and data-sentry-source-file attributes at build
time. This enables searching Replays by component name, seeing component names in breadcrumbs, and performance
monitoring — previously only available with webpack builds.
This feature requires Next.js 16+ and is currently behind an experimental flag:
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 unable to resolve dependency tree
npm error
npm error While resolving: @ecrituresnumerique/stylo-front@3.10.1
npm error Found: vite@7.3.1
npm error node_modules/vite
npm error vite@"~7.3" from the root project
npm error
npm error Could not resolve dependency:
npm error peer vite@"^8.0.0" from @vitejs/plugin-react@6.0.1
npm error node_modules/@vitejs/plugin-react
npm error @vitejs/plugin-react@"~6.0.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/2026-03-28T03_12_32_572Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2026-03-28T03_12_32_572Z-debug-0.log
ggrossetie
changed the title
chore(deps): update react dependencies (major)
Update React dependencies (major)
Apr 3, 2026
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
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~5.1→~6.0.0^0.564.0→^1.0.0~18.3→~19.2.0~18.3→~19.2.0^2.0.5→^3.0.0Release Notes
getsentry/sentry-javascript (@sentry/react)
v10.49.0Compare Source
Important Changes
feat(browser): Add View Hierarchy integration (#14981)
A new
viewHierarchyIntegrationcaptures the DOM structure when an error occurs, providing a snapshot of the page state for debugging. Enable it in your Sentry configuration:feat(cloudflare): Split alarms into multiple traces and link them (#19373)
Durable Object alarms now create separate traces for each alarm invocation, with proper linking between related alarms for better observability.
feat(cloudflare): Enable RPC trace propagation with
enableRpcTracePropagation(#19991, #20345)A new
enableRpcTracePropagationoption enables automatic trace propagation for Cloudflare RPC calls via.fetch(), ensuring distributed traces flow correctly across service bindings.feat(core): Add
enableTruncationoption to AI integrations (#20167, #20181, #20182, #20183, #20184)All AI integrations (OpenAI, Anthropic, Google GenAI, LangChain, LangGraph) now support an
enableTruncationoption to control whether large AI inputs/outputs are truncated.feat(opentelemetry): Vendor
AsyncLocalStorageContextManager(#20243)The OpenTelemetry context manager is now vendored internally, reducing external dependencies and ensuring consistent behavior across environments.
Other Changes
rewriteSourcestop level option (#20142)eventLoopBlockIntegration(#20108)conversation_idonly ongen_aispans (#20274)ai.operationIdfor Vercel AI V6 operation name mapping (#20285)reader.closedrejection fromreleaseLock()in streaming (#20187)Internal Changes
findInjectionIndexAfterDirectivesfor better readability (#20310)@opentelemetry/resourceswith inlinegetSentryResource()(#20327)v10.48.0Compare Source
Important Changes
feat(aws-serverless): Ship Lambda extension in npm package for container image Lambdas (#20133)
The Sentry Lambda extension is now included in the npm package, enabling container image-based Lambda functions to use it. Copy the extension files into your Docker image and set the
tunneloption:This works with any Sentry SDK (
@sentry/aws-serverless,@sentry/sveltekit,@sentry/node, etc.).feat(cloudflare): Support basic WorkerEntrypoint (#19884)
withSentrynow supports instrumenting classes extending Cloudflare'sWorkerEntrypoint. This instrumentsfetch,scheduled,queue, andtailhandlers.ref(core): Unify .do* span ops to
gen_ai.generate_content(#20074)All Vercel AI
do*spans (ai.generateText.doGenerate,ai.streamText.doStream,ai.generateObject.doGenerate,ai.streamObject.doStream) now use a single unified span opgen_ai.generate_contentinstead of separate ops likegen_ai.generate_text,gen_ai.stream_text,gen_ai.generate_object, andgen_ai.stream_object.ref(core): Remove provider-specific AI span attributes in favor of
gen_aiattributes in sentry conventions (#20011)The following provider-specific span attributes have been removed from the OpenAI and Anthropic AI integrations. Use the standardized
gen_ai.*equivalents instead:openai.response.idgen_ai.response.idopenai.response.modelgen_ai.response.modelopenai.usage.prompt_tokensgen_ai.usage.input_tokensopenai.usage.completion_tokensgen_ai.usage.output_tokensopenai.response.timestampanthropic.response.timestampIf you reference these attributes in hooks (e.g.
beforeSendTransaction), update them to thegen_ai.*equivalents.feat(core): Support embeddings in LangChain (#20017)
Adds instrumentation for LangChain embeddings (
embedQuery,embedDocuments), creatinggen_ai.embeddingsspans. In Node.js, embedding classes from@langchain/openai,@langchain/google-genai,@langchain/mistralai, and@langchain/google-vertexaiare auto-instrumented. For other runtimes, use the newinstrumentLangChainEmbeddingsAPI:Other Changes
denoRuntimeMetricsIntegration(#20023)5.2.0(#20122)sentryOnError(#20120)flagscontext to error events (#20116)Internal Changes
tsconfig-templatefolder (#20067)mshick/add-pr-comment(#20078)ToolLoopAgent(#20087)v10.47.0Compare Source
Important Changes
feat(node-core): Add OTLP integration for node-core/light (#19729)
Added
otlpIntegrationat@sentry/node-core/light/otlpfor users who managetheir own OpenTelemetry setup and want to send trace data to Sentry without
adopting the full
@sentry/nodeSDK.The integration links Sentry errors to OTel traces and exports spans to Sentry via OTLP.
feat(node, bun): Add runtime metrics integrations for Node.js and Bun (#19923, #19979)
New
nodeRuntimeMetricsIntegrationandbunRuntimeMetricsIntegrationautomatically collect runtime health metrics and send them to Sentry on a configurable interval (default: 30s). Collected metrics include memory (RSS, heap used/total), CPU utilization, event loop utilization, and process uptime. Node additionally collects event loop delay percentiles (p50, p99). Extra metrics like CPU time and external memory are available as opt-in.feat(core): Support embedding APIs in google-genai (#19797)
Adds instrumentation for the Google GenAI
embedContentAPI, creatinggen_ai.embeddingsspans.feat(browser): Add
elementTimingIntegrationfor tracking element render and load times (#19869)The new
elementTimingIntegrationcaptures Element Timing API data as Sentry metrics. It emitselement_timing.render_timeandelement_timing.load_timedistribution metrics for elements annotated with theelementtimingHTML attribute.Other Changes
sentry-traceandbaggageheaders on outgoing requests (#19960)Internal Changes
nodeRuntimeMetricsIntegration(#19989)v10.46.0Compare Source
Important Changes
feat(elysia):
@sentry/elysia- Alpha Release (#19509)New Sentry SDK for the Elysia web framework, supporting both Bun and Node.js runtimes.
Features
onErrorhook; 3xx/4xx ignored by default. Customizable withshouldHandleError.GET /users/:id).sentry-traceandbaggageheaders propagated automatically on incoming/outgoing requests.Usage
Other Changes
ctxargument toWorkflow.douser callback (#19891).withResponse()on Anthropic instrumentation (#19935)internal_erroras span status for Vercel error spans (#19921)nodeto nest metadata (#19875)Internal Changes
file-typedependency (#19824)buildMethodPathutility from openai (#19969)@elysiajs/opentelemetrydependency (#19947)Work in this release was contributed by @roli-lpci. Thank you for your contributions!
Important Changes
feat(node): Add
nodeRuntimeMetricsIntegrationfor automatic Node.js runtime metrics (#19923)The new
nodeRuntimeMetricsIntegrationautomatically collects Node.js runtime health metrics and sends them to Sentry. Eight metrics are emitted by default every 30 seconds: memory (RSS, heap used/total), CPU utilization, event loop delay (p50, p99), event loop utilization, and process uptime. Additional metrics are available as opt-in.v10.45.0Compare Source
Important Changes
feat(remix): Server Timing Headers Trace Propagation (#18653)
The Remix SDK now supports automatic trace propagation via
Server-Timingresponse headers to continue pageload traces on the client side.This means, you no longer have to define a custom
metafunction to add Sentry<meta>tags to your page as previously.We'll update out Remix tracing docs after this release.
Other Changes
withSentry(#19836)SpanStatusTypefor langchain/google-genai (#19863)Internal Changes
v10.44.0Compare Source
Important Changes
feat(effect): Add
@sentry/effectSDK (Alpha) (#19644)This release introduces
@sentry/effect, a new SDK for Effect.ts applications. The SDK provides Sentry integration via composable Effect layers for both Node.js and browser environments.Compose the
effectLayerwith optional tracing, logging, and metrics layers to instrument your Effect application:Alpha features are still in progress, may have bugs and might include breaking changes. Please reach out on GitHub if you have any feedback or concerns.
feat(astro): Add Astro 6 support (#19745)
This release enables full support for Astro v6 by adjusting our Astro SDK's middleware to some Astro-internal
changes. We cannot yet guarantee full support for server-islands, due to a bug in Astro v6
but we'll follow up on this once the bug is fixed.
feat(hono): Add basic instrumentation for Node runtime (#19817)
Adds a new package
@sentry/hono/node(alpha) with basic instrumentation for Hono applications running in Node.js.The Hono middleware for Cloudflare (
@sentry/hono/cloudflare- alpha) comes with fixes, and it's now possible to access the Cloudflare Worker Bindings (env) from the options' callback.Start using the new Hono middlewares by installing
@sentry/honoand importing the respective middleware for your runtime.More instructions can be found in the Hono readme.
Alpha features are still in progress, may have bugs and might include breaking changes. Please reach out on GitHub if you have any feedback or concerns.
feat(nestjs): Instrument
@nestjs/bullmq@Processordecorator (#19759)Automatically capture exceptions and create transactions for BullMQ queue processors in NestJS applications.
When using the
@Processordecorator from@nestjs/bullmq, the SDK now automatically wraps theprocess()methodto create
queue.processtransactions with proper isolation scopes, preventing breadcrumb and scope leakage betweenjobs and HTTP requests. Errors thrown in processors are captured with the
auto.queue.nestjs.bullmqmechanism type.Requires
@nestjs/bullmqv10.0.0 or later.feat(nestjs): Instrument
@nestjs/scheduledecorators (#19735)Automatically capture exceptions thrown in
@Cron,@Interval, and@Timeoutdecorated methods.Previously, exceptions in
@Cronmethods were only captured if you used theSentryCrondecorator. Now they arecaptured automatically. The exception mechanism type changed from
auto.cron.nestjs.asynctoauto.function.nestjs.cron. If you have Sentry queries or alerts that filter on the old mechanism type, update themaccordingly.
feat(node): Expose
headersToSpanAttributesoption onnativeNodeFetchIntegration()(#19770)Response headers like
http.response.header.content-lengthwere previously captured automatically on outgoingfetch spans but are now opt-in since
@opentelemetry/instrumentation-undici@0.22.0. You can now configure whichheaders to capture via the
headersToSpanAttributesoption.Other Changes
sentry.timestamp.sequenceattribute for timestamp tie-breaking (#19421)sendDefaultPiisetting in langchain and langgraph in non-node environments (#19813)@nestjs/event-emitterinstrumentation (#19725)lastEventIdwhen error is thrown in component render (#19764)Internal Changes
skill-creatorand update managed agent skills (#19713)@sentry/honoalpha release (#19828)"*"(#19756)sdkNamefor craft (#19736)vite-plugin-federation(#19778)v10.43.0Compare Source
Important Changes
feat(nextjs): Add Turbopack support for React component name annotation (#19604)
We added experimental support for React component name annotation in Turbopack builds. When enabled, JSX elements
are annotated with
data-sentry-component,data-sentry-element, anddata-sentry-source-fileattributes at buildtime. This enables searching Replays by component name, seeing component names in breadcrumbs, and performance
monitoring — previously only available with webpack builds.
This feature requires Next.js 16+ and is currently behind an experimental flag:
feat(hono): Instrument middlewares
app.use()(#19611)Hono middleware registered via
app.use()is now automatically instrumented, creating spans for each middleware invocation.Other Changes
tracePropagationoption to http and fetch integrations (#19712)instrumentDurableObjectStorage(#19662)Internal Changes
build:devcommand (#19586)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.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Renovate Bot.