Skip to content

Update dependency @sentry/node to v10 - autoclosed#300

Closed
BacLuc wants to merge 1 commit intodevelfrom
renovate/major-sentry-javascript-monorepo
Closed

Update dependency @sentry/node to v10 - autoclosed#300
BacLuc wants to merge 1 commit intodevelfrom
renovate/major-sentry-javascript-monorepo

Conversation

@BacLuc
Copy link
Owner

@BacLuc BacLuc commented Aug 3, 2025 •
edited
Loading

This PR contains the following updates:

Package Change Age Confidence
@sentry/node (source) 9.46.0 -> 10.17.0 age confidence

Release Notes

getsentry/sentry-javascript (@​sentry/node)

v10.17.0

Compare 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_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)

v10.16.0

Compare Source

  • feat(logs): Add internal replay_is_buffering flag (#​17752)
  • feat(react-router): Update loadContext type to be compatible with middleware (#​17758)
  • feat(replay/logs): Only attach sampled replay Ids to logs (#​17750)
  • fix(browser): Use current start timestamp for CLS span when CLS is 0 (#​17800)
  • fix(core): Prevent instrumentAnthropicAiClient breaking MessageStream api (#​17754)
  • fix(nextjs): Don't use chalk in turbopack config file (#​17806)
  • fix(react): Do not send additional navigation span on pageload (#​17799)
Internal Changes
  • build(aws): Ensure AWS build cache does not keep old files (#​17776)
  • chore: Add publish_release command (#​17797)
  • ref(aws-serverless): Add resolution for import-in-the-middle when building the Lambda layer (#​17780)
  • ref(aws-serverless): Improve README with better examples (#​17787)
  • ref(core): Improve promise buffer (#​17788)
  • Revert "test(e2e): Pin import-in-the-middle@1.14.2 due to @vercel/nft incompatibility (#​17777)" (#​17784)
  • test(e2e): Pin import-in-the-middle@1.14.2 due to @vercel/nft incompatibility (#​17777)
  • test(nextjs): Add route handler tests for turbopack (#​17515)
  • test(react-router): Test v8 middleware (#​17783)

v10.15.0

Compare Source

Important Changes

  • 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)
  • build: Add @typescript-eslint/no-unnecessary-type-assertion rule (#​17728)
  • build: Update TS target to es2020 everywhere (#​17709)
  • chore: Add external contributor to CHANGELOG.md (#​17745)

Work in this release was contributed by @​Karibash. Thank you for your contribution!

v10.14.0

Compare 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
  • fix(nextjs): Display updated turbopack warnings (#​17737)
  • ref(core): Wrap isolationscope in WeakRef when storing it on spans (#​17712)
Internal Changes
  • test(node): Avoid using specific port for node-integration-tests (#​17729)
  • test(nuxt): Update Nuxt version and add Nitro $fetch test (#​17713)

v10.13.0

Compare 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:

    Sentry.init({
  //...
  integrations: [
    // 1. Enable manual pageload reporting
    Sentry.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)
  • feat(deps): bump @​sentry/cli from 2.52.0 to 2.53.0 (#​17652)
  • feat(node): Add extra platforms to os context (#​17720)
  • fix(browser): Ensure idle span duration is adjusted when child spans are ignored (#​17700)
  • fix(core): Ensure builtin stack frames don't affect thirdPartyErrorFilterIntegration (#​17693)
  • fix(core): Fix client hook edge cases around multiple callbacks (#​17706)
  • fix(nextjs): Enable fetch span when OTel setup is skipped (#​17699)
  • fix(node): Fix this context for vercel AI instrumentation (#​17681)
Internal Changes
  • chore: Add external contributor to CHANGELOG.md (#​17725)
  • chore: Add link to build and test icon in readme (#​17719)
  • chore(nuxt): Bump Vite and Rollup plugins (#​17671)
  • chore(repo): Add changelog entry for reportPageLoaded (#​17724)
  • ci: Fix lookup of changed E2E test apps (#​17707)
  • ci(test-matrix): Add logs for getTestMatrix (#​17673)
  • ref: Avoid some usage of SyncPromise where not needed (#​17641)
  • ref(core): Add debug log when dropping a span via ignoreSpans (#​17692)
  • ref(core): Avoid looking up anthropic-ai integration options (#​17694)
  • ref(core): Streamline module_metadata assignment and cleanup functions (#​17696)
  • ref(remix): Avoid unnecessary error wrapping HandleDocumentRequestFunction (#​17680)
  • Revert "[Gitflow] Merge master into develop"

Work in this release was contributed by @​Olexandr88. Thank you for your contribution!

v10.12.0

Compare Source

Important Changes

  • ref: Add and Adjust error event mechanism values

    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.

    Relevant PRs

    Released in 10.12.0:

    • ref(angular): Adjust ErrorHandler event mechanism (#​17608)
    • ref(astro): Adjust mechanism on error events captured by astro middleware (#​17613)
    • ref(aws-severless): Slightly adjust aws-serverless mechanism type (#​17614)
    • ref(bun): Adjust mechanism of errors captured in Bun.serve (#​17616)
    • ref(cloudflare): Adjust event mechanisms and durable object origin (#​17618)
    • ref(core): Adjust mechanism in captureConsoleIntegration (#​17633)
    • ref(core): Adjust MCP server error event mechanism (#​17622)
    • ref(core): Simplify linkedErrors mechanism logic (#​17600)
    • 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.

Other Changes
  • feat(browser): Add timing and status atttributes to resource spans (#​17562)
  • feat(cloudflare,vercel-edge): Add support for Anthropic AI instrumentation (#​17571)
  • feat(core): Add Consola integration (#​17435)
  • feat(deps): Update OpenTelemetry dependencies (#​17569)
  • feat(core): Export TracesSamplerSamplingContext type (#​17523)
  • feat(deno): Add OpenTelemetry support and vercelAI integration (#​17445)
  • feat(node-core): Remove experimental note from winston api (#​17626)
  • feat(node): Ensure prismaIntegration works with Prisma v5 (#​17595)
  • feat(node): Tidy existing ESM loader hook (#​17566)
  • feat(sveltekit): Align build time options with shared type (#​17413)
  • fix(core): Fix error handling when sending envelopes (#​17662)
  • fix(browser): Always start navigation as root span (#​17648)
  • fix(browser): Ensure propagated parentSpanId stays consistent during trace in TwP mode (#​17526)
  • fix(cloudflare): Initialize once per workflow run and preserve scope for step.do (#​17582)
  • fix(nextjs): Add edge polyfills for nextjs-13 in dev mode (#​17488)
  • fix(nitro): Support nested _platform properties in Nitro 2.11.7+ (#​17596)
  • fix(node): Preserve synchronous return behavior for streamText and other methods for AI (#​17580)
  • ref(node): Inline types imported from shimmer (#​17597) - ref(nuxt): Add and adjust mechanism.type in error events (#​17599)
  • ref(browser): Improve fetchTransport error handling (#​17661)
Internal Changes
  • chore: Add changelog note about mechanism changes (#​17632)
  • chore(aws): Update README.md (#​17601)
  • chore(deps): bump hono from 4.7.10 to 4.9.7 in /dev-packages/e2e-tests/test-applications/cloudflare-hono (#​17630)
  • chore(deps): bump next from 14.2.25 to 14.2.32 in /dev-packages/e2e-tests/test-applications/nextjs-app-dir (#​17627)
  • chore(deps): bump next from 14.2.25 to 14.2.32 in /dev-packages/e2e-tests/test-applications/nextjs-pages-dir (#​17620)
  • chore(deps): bump next from 14.2.29 to 14.2.32 in /dev-packages/e2e-tests/test-applications/nextjs-orpc (#​17494)
  • chore(deps): bump next from 14.2.30 to 14.2.32 in /dev-packages/e2e-tests/test-applications/nextjs-14 (#​17628)
  • chore(repo): Rename .claude/settings.local.json to .claude/settings.json (#​17591)
  • docs(issue-template): Add note about prioritization (#​17590)
  • ref(core): Streamline event processor handling (#​17634)
  • test(angular): Bump TS version to 5.9.0 in Angular 20 e2e test (#​17605)
  • test(nextjs): Remove Next 13 and pin Next 14 canary and latest tests (#​17577)
  • test(react-router): Unflake flushIfServerless test (#​17610)

v10.11.0

Compare 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.enableLambdaExtension in your Sentry config like this:

    Sentry.init({
  dsn: '<YOUR_DSN>',
  _experiments: {
    enableLambdaExtension: true,
  },
});
Other Changes
  • feat(core): Add replay id to logs (#​17563)
  • feat(core): Improve error handling for Anthropic AI instrumentation (#​17535)
  • feat(deps): bump @​opentelemetry/instrumentation-ioredis from 0.51.0 to 0.52.0 (#​17557)
  • feat(node): Add incoming request headers as OTel span attributes (#​17475)
  • fix(astro): Ensure traces are correctly propagated for static routes (#​17536)
  • fix(react): Remove handleExistingNavigation (#​17534)
  • 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)
Internal Changes
  • chore: Use proper test-utils dependency in workspace (#​17538)
  • chore(test): Remove geist font (#​17541)
  • ci: Check for stable lockfile (#​17552)
  • ci: Fix running of only changed E2E tests (#​17551)
  • ci: Remove project automation workflow (#​17508)
  • test(node-integration-tests): pin ai@5.0.30 to fix test fails (#​17542)

v10.10.0

Compare Source

Important Changes
  • 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 withSentryConfig for automatic source maps uploads when building a Next.js app with next build --turbopack.
When set we:

  • Automatically enable source map generation for turbopack client files (if not explicitly disabled)
  • Upload generated source maps to Sentry at the end of the build by leveraging a Next.js compiler hook.
Other Changes
  • feat(feedback): Add more labels so people can configure Highlight and Hide labels (#​17513)
  • fix(node): Add origin for OpenAI spans & test auto instrumentation (#​17519)

v10.9.0

Compare Source

Important Changes
  • feat(node): Update httpIntegration handling of incoming requests (#​17371)

This version updates the handling of the Node SDK of incoming requests. Instead of relying on @​opentelemetry/instrumentation-http, we now handle incoming request instrumentation internally, ensuring that we can optimize performance as much as possible and avoid interop problems.

This change should not affect you, unless you're relying on very in-depth implementation details. Importantly, this also drops the _experimentalConfig option of the integration - this will no longer do anything.
Finally, you can still pass instrumentation.{requestHook,responseHook,applyCustomAttributesOnSpan} options, but they are deprecated and will be removed in v11. Instead, you can use the new incomingRequestSpanHook configuration option if you want to adjust the incoming request span.

Other Changes
  • feat(browser): Add replay.feedback CDN bundle (#​17496)
  • feat(browser): Export sendFeedback from CDN bundles (#​17495)
  • fix(astro): Ensure span name from beforeStartSpan isn't overwritten (#​17500)
  • fix(browser): Ensure source is set correctly when updating span name in-place in beforeStartSpan (#​17501)
  • fix(core): Only set template attributes on logs if parameters exist (#​17480)
  • fix(nextjs): Fix parameterization for root catchall routes (#​17489)
  • fix(node-core): Shut down OTel TraceProvider when calling Sentry.close() (#​17499)
Internal Changes
  • chore: Add changelog script back to package.json (#​17517)
  • chore: Ensure prettier is run on all files (#​17497)
  • chore: Ignore prettier commit for git blame (#​17498)
  • chore: Remove experimental from Nuxt SDK package description (#​17483)
  • ci: Capture overhead in node app (#​17420)
  • ci: Ensure we fail on cancelled jobs (#​17506)
  • ci(deps): bump actions/checkout from 4 to 5 (#​17505)
  • ci(deps): bump actions/create-github-app-token from 2.0.6 to 2.1.1 (#​17504)
  • test(aws): Improve reliability on CI (#​17502)

v10.8.0

Compare Source

Important Changes

  • feat(sveltekit): Add Compatibility for builtin SvelteKit Tracing (#​17423)

    This release makes the @sentry/sveltekit SDK compatible with SvelteKit's native observability support introduced in SvelteKit version 2.31.0.
    If you enable both, instrumentation and tracing, the SDK will now initialize early enough to set up additional instrumentation like database queries and it will pick up spans emitted from SvelteKit.

    We will follow up with docs how to set up the SDK soon.
    For now, If you're on SvelteKit version 2.31.0 or newer, you can easily opt into the new feature:

    1. Enable experimental tracing and instrumentation support in svelte.config.js:

    2. Move your Sentry.init() call from src/hooks.server.(js|ts) to the new instrumentation.server.(js|ts) file:

      // instrumentation.server.ts
import * as Sentry from '@&#8203;sentry/sveltekit';

Sentry.init({
  dsn: '...',
  // rest of your config
});

      The rest of your Sentry config in hooks.server.ts (sentryHandle and handleErrorWithSentry) should stay the same.

    If you prefer to stay on the hooks-file based config for now, the SDK will continue to work as previously.

    Thanks to the Svelte team and @​elliott-with-the-longest-name-on-github for implementing observability support and for reviewing our PR!

Other Changes
  • fix(react): Avoid multiple name updates on navigation spans (#​17438)
Internal Changes
  • test(profiling): Add tests for current state of profiling (#​17470)

v10.7.0

Compare Source

Important Changes
  • feat(cloudflare): Add instrumentPrototypeMethods option to instrument RPC methods for DurableObjects (#​17424)

By default, Sentry.instrumentDurableObjectWithSentry will not wrap any RPC methods on the prototype. To enable wrapping for RPC methods, set instrumentPrototypeMethods to true or, if performance is a concern, a list of only the methods you want to instrument:

class MyDurableObjectBase extends DurableObject<Env> {
  method1() {
    // ...
  }

  method2() {
    // ...
  }

  method3() {
    // ...
  }
}
// Export your named class as defined in your wrangler config
export const MyDurableObject = Sentry.instrumentDurableObjectWithSentry(
  (env: Env) => ({
    dsn: "https://ac49b7af3017c458bd12dab9b3328bfc@o4508482761982032.ingest.de.sentry.io/4508482780987481",
    tracesSampleRate: 1.0,
    instrumentPrototypeMethods: ['method1', 'method3'],
  }),
  MyDurableObjectBase,
);

v10.6.0

Compare Source

Important Changes
  • feat(node): Add Anthropic AI integration (#​17348)

This release adds support for automatically tracing Anthropic AI SDK requests, providing better observability for AI-powered applications.

  • fix(core): Instrument invoke_agent root span, and support Vercel ai v5 (#​17395)

This release makes the Sentry vercelAiIntegration compatible with version 5 of Vercel ai.

The Sentry Nuxt SDK is now considered stable and no longer in beta!

Other Changes
  • feat(astro): Align options with shared build time options type (#​17396)
  • feat(aws): Add support for automatic wrapping in ESM (#​17407)
  • feat(node): Add an instrumentation interface for Hono (#​17366)
  • fix(browser): Use DedicatedWorkerGlobalScope global object type in registerWebWorker (#​17447)
  • fix(core): Only consider ingest endpoint requests when checking isSentryRequestUrl (#​17393)
  • fix(node): Fix preloading of instrumentation (#​17403)
Internal Changes
  • chore: Add external contributor to CHANGELOG.md (#​17449)
  • chore(deps): bump astro from 4.16.18 to 4.16.19 in /dev-packages/e2e-tests/test-applications/astro-4 (#​17434)
  • test(e2e/firebase): Fix firebase e2e test failing due to outdated rules file (#​17448)
  • test(nextjs): Fix canary tests (#​17416)
  • test(nuxt): Don't rely on flushing for lowQualityTransactionFilter (#​17406)
  • test(solidstart): Don't rely on flushing for lowQualityTransactionFilter (#​17408)

v10.5.0

Compare Source

Internal Changes
  • chore(repo): Adjust "Publishing a Release" document to include internal changes section in changelog (#​17374)
  • test(aws): Run E2E tests with AWS SAM (#​17367)
  • test(node): Add tests for full http.server span attribute coverage (#​17373)

Work in this release was contributed by @​ha1fstack. Thank you for your contribution!

v10.4.0

Compare Source

Important Changes
  • fix(browser): Ensure IP address is only inferred by Relay if sendDefaultPii is true

This release includes a fix for a behaviour change
that was originally introduced with v9 of the SDK: User IP Addresses should only be added to Sentry events automatically,
if sendDefaultPii was set to true.

However, the change in v9 required further internal adjustment, which should have been included in v10 of the SDK.
Unfortunately, the change did not make it into the initial v10 version but is now applied with 10.4.0.
There is no API breakage involved and hence it is safe to update.
However, after updating the SDK, events (errors, traces, replays, etc.) sent from the browser, will only include
user IP addresses, if you set sendDefaultPii: true in your Sentry.init options.

We apologize for any inconvenience caused!

  • feat(node): Add ignoreStaticAssets (#​17370)

This release adds a new option to httpIntegration to ignore requests for static assets (e.g. favicon.xml or robots.txt). The option defaults to true, meaning that going forward, such requests will not be traced by default. You can still enable tracing for these requests by setting the option to false:

Sentry.init({
  integrations: [
    Sentry.httpIntegration({
      // defaults to true, set to false to enable traces for static assets
      ignoreStaticAssets: false,
    }),
  ],
});
Other Changes
  • fix(nuxt): Do not drop parametrized routes (#​17357)
Internal Changes
  • ref(node): Split up incoming & outgoing http handling (#​17358)
  • test(node): Enable additionalDependencies in integration runner (#​17361)

v10.3.0

Compare Source

  • feat(core): MCP Server - Capture prompt results from prompt function calls (#​17284)
  • feat(bun): Export skipOpenTelemetrySetup option (#​17349)
  • feat(sveltekit): Streamline build logs (#​17306)
  • fix(browser): Handle data urls in errors caught by globalHandlersIntegration (#​17216)
  • fix(browser): Improve navigation vs. redirect detection (#​17275)
  • fix(react-router): Ensure source map upload fails silently if Sentry CLI fails (#​17081)
  • fix(react): Add support for React Router sub-routes from handle (#​17277)

v10.2.0

Compare Source

Important Changes
  • feat(core): Add ignoreSpans option (#​17078)

This release adds a new top-level Sentry.init option, ignoreSpans, that can be used as follows:

Sentry.init({
  ignoreSpans: [
    'partial match', // string matching on the span name
    /regex/, // regex matching on the span name
    {
      name: 'span name',
      op: /http.client/,
    },
  ],
});

Spans matching the filter criteria will not be recorded. Potential child spans of filtered spans will be re-parented, if possible.

  • feat(cloudflare,vercel-edge): Add support for OpenAI instrumentation (#​17338)

Adds support for OpenAI manual instrumentation in @sentry/cloudflare and @sentry/vercel-edge.

To instrument the OpenAI client, wrap it with Sentry.instrumentOpenAiClient and set recording settings.

import * as Sentry from '@&#8203;sentry/cloudflare';
import OpenAI from 'openai';

const openai = new OpenAI();
const client = Sentry.instrumentOpenAiClient(openai, { recordInputs: true, recordOutputs: true });

// use the wrapped client
  • ref(aws): Remove manual span creation (#​17310)

The startTrace option is deprecated and will be removed in a future major version. If you want to disable tracing, set SENTRY_TRACES_SAMPLE_RATE to 0.0. instead. As of today, the flag does not affect traces anymore.

Other Changes

v10.1.0

Compare Source

  • feat(nuxt): Align build-time options to follow bundler plugins structure (#​17255)
  • fix(browser-utils): Ensure web vital client hooks unsubscribe correctly ([#​17272

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.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

  • If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

@BacLuc BacLuc added the renovate label Aug 3, 2025
@BacLuc BacLuc force-pushed the devel branch 3 times, most recently from 90ed3e5 to 4777eff Compare August 3, 2025 14:27
@BacLuc
Copy link
Owner Author

BacLuc commented Aug 3, 2025

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

@BacLuc BacLuc force-pushed the renovate/major-sentry-javascript-monorepo branch from 601c8cd to 6f3b7e8 Compare October 7, 2025 20:03
@BacLuc BacLuc changed the title fix(deps): update sentry-javascript monorepo to v10 (major) Update dependency @sentry/node to v10 Oct 7, 2025
@BacLuc BacLuc force-pushed the renovate/major-sentry-javascript-monorepo branch from 6f3b7e8 to 31acf30 Compare October 7, 2025 20:17
@BacLuc BacLuc changed the title Update dependency @sentry/node to v10 Update dependency @sentry/node to v10 - autoclosed Dec 14, 2025
@BacLuc BacLuc closed this Dec 14, 2025
@BacLuc BacLuc deleted the renovate/major-sentry-javascript-monorepo branch December 14, 2025 17:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

renovate

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@BacLuc