chore(deps): update all dependencies (major)#2046
Open
renovate[bot] wants to merge 1 commit intomainfrom
Open
Conversation
592afae to
e7fc685
Compare
This was referenced Jan 10, 2025
Merged
c47844e to
077a66f
Compare
077a66f to
e874728
Compare
e874728 to
b652963
Compare
This was referenced Jan 14, 2025
a2b183c to
92a5d80
Compare
This was referenced Jan 17, 2025
92a5d80 to
07f2ff2
Compare
87bc345 to
df60168
Compare
bddb5d3 to
d40e5de
Compare
6965e70 to
62a2b8c
Compare
08b8f1f to
c1ef340
Compare
7f3da64 to
83be6c3
Compare
04411f2 to
9df4304
Compare
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.
This PR contains the following updates:
8.55.0→10.46.029.5.14→30.0.018.3.27→19.2.1418.3.7→19.2.310.0.0→11.0.03.2.4→4.1.13.2.4→4.1.1v4→v6v4→v8v4→v6v5→v6v4→v6v4→v79.2.1→10.1.1==6.2.6→==7.0.5v3→v4^9.0.0→^10.0.09.1.2→10.1.810.5.0→13.0.627.4.0→29.0.120→2422→2424→25~= 2.17→~=3.618.3.1→19.2.418.3.1→19.2.414.3.8→15.0.09.1.0→10.1.0==6.4.0→==7.4.07→816.12.0→17.5.014.0.0→17.0.06.0.4→8.1.15.9.3→6.0.27.3.1→8.0.3^3.2.4→^4.0.0Release Notes
getsentry/sentry-javascript (@sentry/react)
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!
Bundle size 📦
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
Configuration
📅 Schedule: Branch creation - "on the first day of january" (UTC), 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 was generated by Mend Renovate. View the repository job log.