chore(deps): update sentry-javascript monorepo to v10 (major)#734
chore(deps): update sentry-javascript monorepo to v10 (major)#734renovate[bot] wants to merge 1 commit intomasterfrom
Conversation
|
Warning Review the following alerts detected in dependencies. According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.
|
78bc3a4 to
06fe1df
Compare
2dc3a58 to
79788e0
Compare
79788e0 to
0fb716e
Compare
8831d37 to
4f0363a
Compare
84862b1 to
68e1410
Compare
30a42c4 to
4a2dd53
Compare
db163e0 to
4f18732
Compare
3cbc85c to
f853963
Compare
bd05ca5 to
fd22aee
Compare
e3eef83 to
28d6725
Compare
28d6725 to
b1e740b
Compare
a4ff928 to
aff30c2
Compare
2103096 to
9c82b2b
Compare
ec0494b to
16e8012
Compare
9cf47d9 to
fb57ed9
Compare
0ac1176 to
68c343f
Compare
68c343f to
8f0f5cd
Compare
2adfbef to
0be0447
Compare
b28a493 to
173dcdc
Compare
62037dc to
fa9220d
Compare
d1041cb to
3fb4845
Compare
20a8cad to
3d08e0c
Compare
3d08e0c to
2a62e9f
Compare
2a62e9f to
141ebee
Compare
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
dc99737 to
8f7f9d9
Compare
8f7f9d9 to
917faf8
Compare
This PR contains the following updates:
^8.51.0→^10.0.0^8.51.0→^10.0.0Release Notes
getsentry/sentry-javascript (@sentry/node)
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)Bundle size 📦
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)Work in this release was contributed by @dmmulroy, @lithdew, and @smorimoto. Thank you for your contributions!
v10.42.0Compare Source
addVitePlugininstead of deprecatedvite:extendConfig(#19464)Internal Changes
Bundle size 📦
v10.41.0Compare Source
v10.40.0Compare Source
Important Changes
feat(tanstackstart-react): Add global sentry exception middlewares (#19330)
The
sentryGlobalRequestMiddlewareandsentryGlobalFunctionMiddlewareglobal middlewares capture unhandled exceptions thrown in TanStack Start API routes and server functions. Add them as the first entries in therequestMiddlewareandfunctionMiddlewarearrays ofcreateStart():feat(tanstackstart-react)!: Export Vite plugin from
@sentry/tanstackstart-react/vitesubpath (#19182)The
sentryTanstackStartVite plugin is now exported from a dedicated subpath. Update your import:fix(node-core): Reduce bundle size by removing apm-js-collab and requiring pino >= 9.10 (#18631)
In order to keep receiving pino logs, you need to update your pino version to >= 9.10, the reason for the support bump is to reduce the bundle size of the node-core SDK in frameworks that cannot tree-shake the apm-js-collab dependency.
fix(browser): Ensure user id is consistently added to sessions (#19341)
Previously, the SDK inconsistently set the user id on sessions, meaning sessions were often lacking proper coupling to the user set for example via
Sentry.setUser().Additionally, the SDK incorrectly skipped starting a new session for the first soft navigation after the pageload.
This patch fixes these issues. As a result, metrics around sessions, like "Crash Free Sessions" or "Crash Free Users" might change.
This could also trigger alerts, depending on your set thresholds and conditions.
We apologize for any inconvenience caused!
While we're at it, if you're using Sentry in a Single Page App or meta framework, you might want to give the new
'page'session lifecycle a try!This new mode no longer creates a session per soft navigation but continues the initial session until the next hard page refresh.
Check out the docs to learn more!
ref!(gatsby): Drop Gatsby v2 support (#19467)
We drop support for Gatsby v2 (which still relies on webpack 4) for a critical security update in https://github.com/getsentry/sentry-javascript-bundler-plugins/releases/tag/5.0.0
Other Changes
setTheme()to dynamically update feedback widget color scheme (#19430)sourcemaps.filesToDeleteAfterUploadas a top-level option (#19280)ignoreConnectSpansoption topostgresIntegration(#19291)Configuration
📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM, only on Monday ( * 0-3 * * 1 ) (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR was generated by Mend Renovate. View the repository job log.