Repository navigation
fix(deps): update dependency @sentry/node to v11 - #259
renovate[bot] wants to merge 1 commit into
Conversation
◈ PR LensNote renovate[bot] opened this pull request, so PR Lens left it undrawn. Comment
|
|
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.
|
a903679 to
de11daa
Compare
c8bc7be to
8808981
Compare
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
8808981 to
d740f31
Compare
This PR contains the following updates:
^10.73.0→^11.6.0Release Notes
getsentry/sentry-javascript (@sentry/node)
v11.6.0Compare Source
Important Changes
feat(nextjs): Add
@sentry/nextjs/cloudflare(#24998)The new
@sentry/nextjs/cloudflareentry point exportswithSentryfor the Worker entry of a Next.js app on Cloudflare Workers, for example.open-next/worker.jsof OpenNext. It iswithSentryof@sentry/cloudflarewith the Next.js server handling added, so a Next.js app on Workers gets the same spans as on Node.js.feat(server-utils): Add instrumentation for pi-durable (#24993)
The new
piDurableIntegrationtraces agents built with pi-durable: each run, with its model requests and tool calls.fix(core): Correct sleep clock drift on telemetry timestamps (#23054)
When a device sleeps, the
performance.now()clock of the browser stops. Before this change, timestamps of spans and other telemetry recorded after the sleep could be too early. The SDK now detects this drift and corrects its time origin, also for spans created from performance entries. Span end times are now computed from theperformance.now()duration since the span start, like in OpenTelemetry (#24903).Other Changes
Internal Changes
@sentry/nextjs/cloudflare(#25000)no-unsafe-random-apisrule (#25123)Work in this release was contributed by @zkasuran. Thank you for your contribution!
v11.5.0Compare Source
Important Changes
feat(core): Warn on repeated
Sentry.init()and unbind the client onclose()(#24962)Sentry.init()now warns when it runs while a client is still active. For now, the new client still replaces the active client, but the active client is not closed, so state from both can mix. CallSentry.init()once, or callawait Sentry.close()before you call it again.Sentry.close()now unbinds the client it closes, so afterclose(),getClient()returnsundefined,isInitialized()returnsfalse, and a laterinit()sets up a new client. In@sentry/cloudflare, later requests no longer reuse the isolate's cached client once it is closed or closing. On the server,@sentry/nextjsand@sentry/remixnow return the active client from a repeatedinit()call, notundefined.Other Changes
code.file.pathtouse cachefill spans (#24988)initinside a request of@sentry/cloudflare(#24996)experimental_telemetry.metadataon gen_ai spans (#24721)beforeSendSpannull return warning (#24129)Internal Changes
@sentry/conventionsto 0.26.0 (#25073)isObjectLikefor object guards (#25058)serverSpanHooks.ts(#24997)nuxt/server(#25093)Work in this release was contributed by @minwookshin. Thank you for your contribution!
v11.4.0Compare Source
v11.3.0Compare Source
Important Changes
Remix 3 support (alpha, may break in minor releases)
feat(nextjs): Add
cache_originspan links touse cachehit spans (#24821)A
cache.getspan for a"use cache"hit now carries a span link (sentry.link.type: 'cache_origin') to thecache.putspan of the request that filled the cache entry, connecting the trace that reads a cached value to the trace that produced it.fix(cloudflare): Don't treat DO constructor work as incoming RPC calls (#24829)
Durable Object constructors now run in their own isolation scope. When work that the constructor starts, for example a
blockConcurrencyWhilecallback, calls a method of the instance, that call is no longer treated as an incoming RPC call, so an error the instance catches itself is no longer reported as unhandled. As a result,Sentry.setTag(),setUser()andsetContext()in a constructor now apply only to that constructor work. They no longer reach laterfetch, RPC oralarminvocations, because the scope they used to write to is shared by every Durable Object and handler in the isolate. UseinitialScopefor static data, and set per-instance data in each handler.fix(effect)!: Change peerDependency to v4 and fix currentSpan (#24940)
@sentry/effectnow requires a stable Effect v4 release. Effect v4 beta and release candidate versions are no longer supported.@sentry/effectis in alpha, so this ships in a minor release.Other Changes
client.sendEnvelope(#24896)Internal Changes
4013fc6to36c7292(#24949)Work in this release was contributed by @Shubham-Padkonde and @tobias-schnabel. Thank you for your contributions!
v11.2.0Compare Source
Important Changes
feat(hono): add orchestrion-based auto-instrumentation (#24497)
Hono is now instrumented automatically. Request spans are named after the matched Hono route, each middleware gets its own span, and errors thrown in handlers are captured.
feat(node/bun): Enable dedupeIntegration by default (#24794)
@sentry/nodeand@sentry/bunnow includededupeIntegrationin their default integrations, like the browser, Deno, Vercel Edge and Cloudflare SDKs. When the same error is captured two times in a row, only the first event is sent. To keep the previous behavior, remove the integration:integrations: defaults => defaults.filter(integration => integration.name !== 'Dedupe').feat(remix): Instrument Remix 3 server requests via fetch-router (#24801)
On Remix 3, the SDK now adds the matched route as
http.route, the response status and a low-cardinality name to thehttp.serverspan of eachfetch-routerrequest. Start the app with--import @sentry/remix/v3/nodein place of--import remix/node-tsx.Other Changes
bunRuntimeMetricsIntegration(#24892)fmt/parameterizemessages (#24770)nextis called (#24854)rolldownOptionsin instrumentation file plugin (#24863)Internal Changes
externallabel on PRs of external contributors (#24825)dedupeIntegration(#24893)test-utils/cloudflare(#24815)Work in this release was contributed by @nabi-noor, @LuccaRebelloToledo, @andasan, @breken-ai, @EmileBrunelle, and @diobriggs. Thank you for your contributions!
v11.1.0Compare Source
Important Changes
feat(server-utils): Auto-instrument MCP servers via orchestrion (#24529)
A new default
mcpServerIntegrationwraps everyMcpServerinstance (from@modelcontextprotocol/serverand@modelcontextprotocol/sdk) when it is created. You no longer need to callwrapMcpServerWithSentrymanually. You can still callwrapMcpServerWithSentryto override options, for examplerecordInputs: false.feat(node): Support Prisma 8 in
prismaIntegration(#24682)prismaIntegrationnow creates aprisma:client:operationspan for each Prisma 8 ORM call, with the database query spans nested below it. No code changes are necessary.feat(server-utils): Add TypeSafe integration (#24703)
A new default
typesafeIntegrationcreates agen_ai.evaluatespan for each TypeSafe Jev call through@typesafe-ai/sdk(TypeSafeClient.systemOne). For runtimes without auto-instrumentation, useinstrumentTypeSafeClient().feat(server-utils): Instrument Vercel AI
experimental_evaluate(#24694)Vercel AI
experimental_evaluatecalls now create agen_ai.evaluatespan, with the state and questions as input messages and the answers as output messages.Other Changes
onErrorcallback toshowReportDialog(#24780)registerHookspath) (#24705)@opentelemetry/apivia the SDK on SvelteKit 3 (#24736)Internal Changes
@sentry/conventionsto 0.24.0 (#24645)@cloudflare/think(#24660)Work in this release was contributed by @camc314, @ihsraham, @zkasuran, @Shubham-Padkonde, and @itz-puneet. Thank you for your contributions!
v11.0.0Compare Source
Version
11.0.0marks a major release of the Sentry JavaScript SDKs containing breaking changes.The goal of this release is to be better compatible with OpenTelemetry, make our integrations work across Node.js, Cloudflare, Bun and Deno through run-time and build-time instrumentation, and make span streaming and more permissive data collection the default.
How To Upgrad
Configuration
📅 Schedule: (UTC)
🚦 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 this update again.
This PR was generated by Mend Renovate. View the repository job log.