fix(deps): update dependency @sentry/browser to v10 #1371

renovate · 2025-07-31T21:38:29Z

Coming soon: The Renovate bot (GitHub App) will be renamed to Mend. PRs from Renovate will soon appear from 'Mend'. Learn more here.

This PR contains the following updates:

Package	Change	Age	Confidence
@sentry/browser (source)	`9.46.0` -> `10.15.0`

Release Notes

getsentry/sentry-javascript (@sentry/browser)

`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!

Bundle size 📦

Path	Size
@sentry/browser	23.69 KB
@sentry/browser - with treeshaking flags	22.24 KB
@sentry/browser (incl. Tracing)	39.49 KB
@sentry/browser (incl. Tracing, Replay)	76.96 KB
@sentry/browser (incl. Tracing, Replay) - with treeshaking flags	66.87 KB
@sentry/browser (incl. Tracing, Replay with Canvas)	81.52 KB
@sentry/browser (incl. Tracing, Replay, Feedback)	93.44 KB
@sentry/browser (incl. Feedback)	40.01 KB
@sentry/browser (incl. sendFeedback)	28.24 KB
@sentry/browser (incl. FeedbackAsync)	33.05 KB
@sentry/react	25.37 KB
@sentry/react (incl. Tracing)	41.42 KB
@sentry/vue	28.11 KB
@sentry/vue (incl. Tracing)	41.25 KB
@sentry/svelte	23.72 KB
CDN Bundle	25.17 KB
CDN Bundle (incl. Tracing)	39.39 KB
CDN Bundle (incl. Tracing, Replay)	74.76 KB
CDN Bundle (incl. Tracing, Replay, Feedback)	80.13 KB
CDN Bundle - uncompressed	73.6 KB
CDN Bundle (incl. Tracing) - uncompressed	116.59 KB
CDN Bundle (incl. Tracing, Replay) - uncompressed	229.02 KB
CDN Bundle (incl. Tracing, Replay, Feedback) - uncompressed	241.48 KB
@sentry/nextjs (client)	43.38 KB
@sentry/sveltekit (client)	39.9 KB
@sentry/node-core	48.85 KB
@sentry/node	149.25 KB
@sentry/node - without tracing	89.79 KB
@sentry/aws-serverless	102.92 KB

`v10.14.0`

Compare Source

Important Changes

feat(cloudflare,vercel-edge): Add support for Google Gen AI instrumentation (#17723)

The SDK now automatically instruments Google's Generative AI operations in Cloudflare Workers and Vercel Edge Runtime environments, providing insights into your AI operations.

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)

Bundle size 📦

Path	Size
@sentry/browser	23.69 KB
@sentry/browser - with treeshaking flags	22.24 KB
@sentry/browser (incl. Tracing)	39.46 KB
@sentry/browser (incl. Tracing, Replay)	76.93 KB
@sentry/browser (incl. Tracing, Replay) - with treeshaking flags	66.84 KB
@sentry/browser (incl. Tracing, Replay with Canvas)	81.49 KB
@sentry/browser (incl. Tracing, Replay, Feedback)	93.41 KB
@sentry/browser (incl. Feedback)	40.01 KB
@sentry/browser (incl. sendFeedback)	28.24 KB
@sentry/browser (incl. FeedbackAsync)	33.05 KB
@sentry/react	25.37 KB
@sentry/react (incl. Tracing)	41.38 KB
@sentry/vue	28.11 KB
@sentry/vue (incl. Tracing)	41.22 KB
@sentry/svelte	23.72 KB
CDN Bundle	25.17 KB
CDN Bundle (incl. Tracing)	39.3 KB
CDN Bundle (incl. Tracing, Replay)	74.66 KB
CDN Bundle (incl. Tracing, Replay, Feedback)	80.04 KB
CDN Bundle - uncompressed	73.6 KB
CDN Bundle (incl. Tracing) - uncompressed	116.34 KB
CDN Bundle (incl. Tracing, Replay) - uncompressed	228.76 KB
CDN Bundle (incl. Tracing, Replay, Feedback) - uncompressed	241.23 KB
@sentry/nextjs (client)	43.36 KB
@sentry/sveltekit (client)	39.87 KB
@sentry/node-core	48.85 KB
@sentry/node	148.68 KB
@sentry/node - without tracing	89.79 KB
@sentry/aws-serverless	102.92 KB

`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 GoogleGenerativeAI (#17625)

The SDK now automatically instruments the @google/generative-ai 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!

Bundle size 📦

Path	Size
@sentry/browser	23.66 KB
@sentry/browser - with treeshaking flags	22.21 KB
@sentry/browser (incl. Tracing)	39.39 KB
@sentry/browser (incl. Tracing, Replay)	76.88 KB
@sentry/browser (incl. Tracing, Replay) - with treeshaking flags	66.78 KB
@sentry/browser (incl. Tracing, Replay with Canvas)	81.44 KB
@sentry/browser (incl. Tracing, Replay, Feedback)	93.35 KB
@sentry/browser (incl. Feedback)	39.99 KB
@sentry/browser (incl. sendFeedback)	28.2 KB
@sentry/browser (incl. FeedbackAsync)	33 KB
@sentry/react	25.33 KB
@sentry/react (incl. Tracing)	41.32 KB
@sentry/vue	28.05 KB
@sentry/vue (incl. Tracing)	41.15 KB
@sentry/svelte	23.68 KB
CDN Bundle	25.14 KB
CDN Bundle (incl. Tracing)	39.22 KB
CDN Bundle (incl. Tracing, Replay)	74.59 KB
CDN Bundle (incl. Tracing, Replay, Feedback)	79.96 KB
CDN Bundle - uncompressed	73.46 KB
CDN Bundle (incl. Tracing) - uncompressed	116.1 KB
CDN Bundle (incl. Tracing, Replay) - uncompressed	228.53 KB
CDN Bundle (incl. Tracing, Replay, Feedback) - uncompressed	240.99 KB
@sentry/nextjs (client)	43.3 KB
@sentry/sveltekit (client)	39.81 KB
@sentry/node-core	48.81 KB
@sentry/node	148.62 KB
@sentry/node - without tracing	89.73 KB
@sentry/aws-serverless	102.86 KB

`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.

feat(deps): Update OpenTelemetry dependencies (#17558)
- @opentelemetry/core bumped to ^2.1.0
- @opentelemetry/context-async-hooks bumped to ^2.1.0
- @opentelemetry/resources bumped to ^2.1.0
- @opentelemetry/sdk-trace-base bumped to ^2.1.0
- @opentelemetry/semantic-conventions bumped to ^1.37.0
- @opentelemetry/instrumentation bumped to ^0.204.0
- @opentelemetry/instrumentation-http bumped to ^0.204.0
- @opentelemetry/instrumentation-amqplib bumped to ^0.51.0
- @opentelemetry/instrumentation-aws-sdk bumped to ^0.59.0
- @opentelemetry/instrumentation-connect bumped to ^0.48.0
- @opentelemetry/instrumentation-dataloader bumped to ^0.22.0
- @opentelemetry/instrumentation-express bumped to ^0.53.0
- @opentelemetry/instrumentation-fs bumped from to ^0.24.0
- @opentelemetry/instrumentation-generic-pool bumped to ^0.48.0
- @opentelemetry/instrumentation-graphql bumped to ^0.52.0
- @opentelemetry/instrumentation-hapi bumped to ^0.51.0
- @opentelemetry/instrumentation-ioredis bumped to ^0.52.0
- @opentelemetry/instrumentation-kafkajs bumped to ^0.14.0
- @opentelemetry/instrumentation-knex bumped to ^0.49.0
- @opentelemetry/instrumentation-koa bumped to ^0.52.0
- @opentelemetry/instrumentation-lru-memoizer bumped to ^0.49.0
- @opentelemetry/instrumentation-mongodb bumped from to ^0.57.0
- @opentelemetry/instrumentation-mongoose bumped from to ^0.51.0
- @opentelemetry/instrumentation-mysql bumped to ^0.50.0
- @opentelemetry/instrumentation-mysql2 bumped to ^0.51.0
- @opentelemetry/instrumentation-nestjs-core bumped to ^0.50.0
- @opentelemetry/instrumentation-pg bumped to ^0.57.0
- @opentelemetry/instrumentation-redis bumped to ^0.53.0
- @opentelemetry/instrumentation-undici bumped to ^0.15.0
- @prisma/instrumentation bumped to 6.15.0

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)

Bundle size 📦

Path	Size
@sentry/browser	23.59 KB
@sentry/browser - with treeshaking flags	22.2 KB
@sentry/browser (incl. Tracing)	39.19 KB
@sentry/browser (incl. Tracing, Replay)	76.63 KB
@sentry/browser (incl. Tracing, Replay) - with treeshaking flags	66.64 KB
@sentry/browser (incl. Tracing, Replay with Canvas)	81.2 KB
@sentry/browser (incl. Tracing, Replay, Feedback)	93.13 KB
@sentry/browser (incl. Feedback)	39.93 KB
@sentry/browser (incl. sendFeedback)	28.13 KB
@sentry/browser (incl. FeedbackAsync)	32.96 KB
@sentry/react	25.27 KB
@sentry/react (incl. Tracing)	41.11 KB
@sentry/vue	27.97 KB
@sentry/vue (incl. Tracing)	40.95 KB
@sentry/svelte	23.62 KB
CDN Bundle	25.14 KB
CDN Bundle (incl. Tracing)	39.05 KB
CDN Bundle (incl. Tracing, Replay)	74.48 KB
CDN Bundle (incl. Tracing, Replay, Feedback)	79.82 KB
CDN Bundle - uncompressed	73.4 KB
CDN Bundle (incl. Tracing) - uncompressed	115.49 KB
CDN Bundle (incl. Tracing, Replay) - uncompressed	227.88 KB
CDN Bundle (incl. Tracing, Replay, Feedback) - uncompressed	240.35 KB
@sentry/nextjs (client)	43.08 KB
@sentry/sveltekit (client)	39.62 KB
@sentry/node-core	48.49 KB
@sentry/node	147.1 KB
@sentry/node - without tracing	90.07 KB
@sentry/aws-serverless	103.06 KB

`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)

Bundle size 📦

Path	Size
@sentry/browser	23.59 KB
@sentry/browser - with treeshaking flags	22.2 KB
@sentry/browser (incl. Tracing)	38.93 KB
@sentry/browser (incl. Tracing, Replay)	76.4 KB
@sentry/browser (incl. Tracing, Replay) - with treeshaking flags	66.43 KB
@sentry/browser (incl. Tracing, Replay with Canvas)	80.97 KB
@sentry/browser (incl. Tracing, Replay, Feedback)	92.81 KB
@sentry/browser (incl. Feedback)	39.88 KB
@sentry/browser (incl. sendFeedback)	28.13 KB
@sentry/browser (incl. FeedbackAsync)	32.92 KB
@sentry/react	25.27 KB
@sentry/react (incl. Tracing)	40.91 KB
@sentry/vue	27.97 KB
@sentry/vue (incl. Tracing)	40.72 KB
@sentry/svelte	23.62 KB
CDN Bundle	25.06 KB
CDN Bundle (incl. Tracing)	38.82 KB
CDN Bundle (incl. Tracing, Replay)	74.25 KB
CDN Bundle (incl. Tracing, Replay, Feedback)	79.56 KB
CDN Bundle - uncompressed	73.2 KB
CDN Bundle (incl. Tracing) - uncompressed	114.83 KB
CDN Bundle (incl. Tracing, Replay) - uncompressed	227.23 KB
CDN Bundle (incl. Tracing, Replay, Feedback) - uncompressed	239.56 KB
@sentry/nextjs (client)	42.86 KB
@sentry/sveltekit (client)	39.38 KB
@sentry/node-core	48.45 KB
@sentry/node	146.74 KB
@sentry/node - without tracing	90.02 KB
@sentry/aws-serverless	103.01 KB

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

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 was generated by Mend Renovate. View the repository job log.

socket-security · 2025-07-31T21:38:52Z

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@sentry/browser@9.46.0 ⏵ 10.15.0

View full report

renovate bot added dependencies help wanted Extra attention is needed labels Jul 31, 2025

renovate bot temporarily deployed to ci July 31, 2025 21:38 Inactive

renovate bot temporarily deployed to production July 31, 2025 21:38 Inactive

renovate bot force-pushed the renovate/major-sentry-javascript-monorepo branch from 16060e4 to b818827 Compare August 4, 2025 14:14

renovate bot temporarily deployed to production August 4, 2025 14:14 Inactive

renovate bot temporarily deployed to ci August 4, 2025 14:14 Inactive

renovate bot force-pushed the renovate/major-sentry-javascript-monorepo branch from b818827 to e753454 Compare August 6, 2025 21:40

renovate bot temporarily deployed to ci August 6, 2025 21:40 Inactive

renovate bot temporarily deployed to production August 6, 2025 21:40 Inactive

renovate bot force-pushed the renovate/major-sentry-javascript-monorepo branch from e753454 to 8e86676 Compare August 8, 2025 12:58

renovate bot temporarily deployed to production August 8, 2025 12:58 Inactive

renovate bot temporarily deployed to ci August 8, 2025 12:58 Inactive

renovate bot force-pushed the renovate/major-sentry-javascript-monorepo branch from 8e86676 to f65394e Compare August 8, 2025 16:35

renovate bot temporarily deployed to production August 8, 2025 16:35 Inactive

renovate bot temporarily deployed to ci August 8, 2025 16:35 Inactive

renovate bot force-pushed the renovate/major-sentry-javascript-monorepo branch from f65394e to b226fbd Compare August 10, 2025 14:24

renovate bot temporarily deployed to ci August 10, 2025 14:24 Inactive

renovate bot temporarily deployed to production August 10, 2025 14:24 Inactive

renovate bot force-pushed the renovate/major-sentry-javascript-monorepo branch from b226fbd to d8b5584 Compare August 11, 2025 17:46

renovate bot temporarily deployed to production August 11, 2025 17:46 Inactive

renovate bot temporarily deployed to ci August 11, 2025 17:46 Inactive

renovate bot force-pushed the renovate/major-sentry-javascript-monorepo branch from d8b5584 to 46184d9 Compare August 12, 2025 19:06

renovate bot temporarily deployed to ci August 12, 2025 19:06 Inactive

renovate bot temporarily deployed to production August 12, 2025 19:06 Inactive

renovate bot force-pushed the renovate/major-sentry-javascript-monorepo branch from 46184d9 to 88f4f4a Compare August 13, 2025 09:14

renovate bot temporarily deployed to ci August 13, 2025 09:14 Inactive

renovate bot temporarily deployed to production August 13, 2025 09:14 Inactive

renovate bot temporarily deployed to ci September 11, 2025 01:11 Inactive

renovate bot had a problem deploying to production September 11, 2025 01:11 Failure

renovate bot force-pushed the renovate/major-sentry-javascript-monorepo branch from f075beb to 67c965c Compare September 16, 2025 16:37

renovate bot had a problem deploying to production September 16, 2025 16:37 Failure

renovate bot temporarily deployed to ci September 16, 2025 16:37 Inactive

renovate bot force-pushed the renovate/major-sentry-javascript-monorepo branch from 67c965c to 316d900 Compare September 17, 2025 17:08

renovate bot had a problem deploying to production September 17, 2025 17:08 Failure

renovate bot temporarily deployed to ci September 17, 2025 17:08 Inactive

renovate bot force-pushed the renovate/major-sentry-javascript-monorepo branch from 316d900 to abf8012 Compare September 19, 2025 02:04

renovate bot had a problem deploying to production September 19, 2025 02:04 Failure

renovate bot temporarily deployed to ci September 19, 2025 02:04 Inactive

renovate bot force-pushed the renovate/major-sentry-javascript-monorepo branch from abf8012 to ef95e13 Compare September 25, 2025 13:31

renovate bot temporarily deployed to ci September 25, 2025 13:31 Inactive

renovate bot had a problem deploying to production September 25, 2025 13:31 Failure

renovate bot force-pushed the renovate/major-sentry-javascript-monorepo branch from ef95e13 to ddfe27c Compare September 25, 2025 19:38

renovate bot temporarily deployed to ci September 25, 2025 19:38 Inactive

renovate bot had a problem deploying to production September 25, 2025 19:38 Failure

renovate bot force-pushed the renovate/major-sentry-javascript-monorepo branch from ddfe27c to 1b01203 Compare September 25, 2025 22:32

renovate bot temporarily deployed to ci September 25, 2025 22:32 Inactive

renovate bot had a problem deploying to production September 25, 2025 22:32 Failure

renovate bot force-pushed the renovate/major-sentry-javascript-monorepo branch from 1b01203 to b528902 Compare September 26, 2025 12:38

renovate bot had a problem deploying to production September 26, 2025 12:38 Failure

renovate bot temporarily deployed to ci September 26, 2025 12:38 Inactive

renovate bot force-pushed the renovate/major-sentry-javascript-monorepo branch from b528902 to 7be0332 Compare September 27, 2025 01:38

renovate bot temporarily deployed to ci September 27, 2025 01:38 Inactive

renovate bot had a problem deploying to production September 27, 2025 01:38 Failure

fix(deps): update dependency @sentry/browser to v10

f7f01a4

renovate bot force-pushed the renovate/major-sentry-javascript-monorepo branch from 7be0332 to f7f01a4 Compare September 27, 2025 17:46

renovate bot deployed to ci September 27, 2025 17:46 Active

renovate bot had a problem deploying to production September 27, 2025 17:46 Failure

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

fix(deps): update dependency @sentry/browser to v10 #1371

fix(deps): update dependency @sentry/browser to v10 #1371

renovate bot commented Jul 31, 2025 •

edited

Loading

Uh oh!

socket-security bot commented Jul 31, 2025 •

edited

Loading

Uh oh!

Uh oh!

fix(deps): update dependency @sentry/browser to v10 #1371

Are you sure you want to change the base?

fix(deps): update dependency @sentry/browser to v10 #1371

Conversation

renovate bot commented Jul 31, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Release Notes

Important Changes

Other Changes

Bundle size 📦

Important Changes

Other Changes

Bundle size 📦

Important Changes

Other Changes

Bundle size 📦

Important Changes

Other Changes

Important Changes

Other Changes

Important Changes

Other Changes

Bundle size 📦

Important Changes

Other Changes

Bundle size 📦

Important Changes

Configuration

Uh oh!

socket-security bot commented Jul 31, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Uh oh!

renovate bot commented Jul 31, 2025 •

edited

Loading

socket-security bot commented Jul 31, 2025 •

edited

Loading