Skip to content

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Sep 13, 2025

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@sentry/node (source) 10.11.0 -> 10.20.0 age adoption passing confidence
@types/node (source) 24.3.1 -> 24.9.1 age adoption passing confidence
discord.js (source) 14.22.1 -> 14.23.2 age adoption passing confidence
dotenv 17.2.2 -> 17.2.3 age adoption passing confidence
mongoose (source) 8.18.1 -> 8.19.2 age adoption passing confidence
typescript (source) 5.9.2 -> 5.9.3 age adoption passing confidence

Release Notes

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

v10.20.0

Compare Source

Important Changes
  • feat(flags): Add Growthbook integration (#​17440)

    Adds a new Growthbook integration for feature flag support.

  • feat(solid): Add support for TanStack Router Solid (#​17735)

    Adds support for TanStack Router in the Solid SDK, enabling better routing instrumentation for Solid applications.

  • feat(nextjs): Support native debugIds in turbopack (#​17853)

    Adds support for native Debug IDs in Turbopack, improving source map resolution and error tracking for Next.js applications using Turbopack. Native Debug ID generation will be enabled automatically for compatible versions.

Other Changes
  • feat(nextjs): Prepare for next 16 bundler default (#​17868)
  • feat(node): Capture pino logger name (#​17930)
  • fix(browser): Ignore React 19.2+ component render measure entries (#​17905)
  • fix(nextjs): Fix createRouteManifest with basePath (#​17838)
  • fix(react): Add POP guard for long-running pageload spans (#​17867)
  • fix(tracemetrics): Send boolean for internal replay attribute (#​17908)
  • ref(core): Add weight tracking logic to browser logs/metrics (#​17901)
Internal Changes - chore(nextjs): Add Next.js 16 peer dependency ([#​17925](https://redirect.github.com/getsentry/sentry-javascript/pull/17925)) - chore(ci): Update Next.js canary testing ([#​17939](https://redirect.github.com/getsentry/sentry-javascript/pull/17939)) - chore: Bump size limit ([#​17941](https://redirect.github.com/getsentry/sentry-javascript/pull/17941)) - test(nextjs): Add next@16 e2e test ([#​17922](https://redirect.github.com/getsentry/sentry-javascript/pull/17922)) - test(nextjs): Update next 15 tests ([#​17919](https://redirect.github.com/getsentry/sentry-javascript/pull/17919)) - chore: Add external contributor to CHANGELOG.md ([#​17915](https://redirect.github.com/getsentry/sentry-javascript/pull/17915)) - chore: Add external contributor to CHANGELOG.md ([#​17928](https://redirect.github.com/getsentry/sentry-javascript/pull/17928)) - chore: Add external contributor to CHANGELOG.md ([#​17940](https://redirect.github.com/getsentry/sentry-javascript/pull/17940))

Work in this release was contributed by @​seoyeon9888, @​madhuchavva and @​thedanchez. Thank you for your contributions!

v10.19.0

Compare Source

  • feat(tracemetrics): Add trace metrics behind an experiments flag (#​17883)
Internal Changes
  • chore: add info latest release for the cursor release command (#​17876)

v10.18.0

Compare Source

Important Changes
  • feat(node): pino integration (#​17584)

    This release adds a new pino integration for Node.js, enabling Sentry to capture logs from the Pino logging library.

  • feat: Remove @​sentry/pino-transport package (#​17851)

    The @sentry/pino-transport package has been removed. Please use the new pino integration in @sentry/node instead.

  • feat(node-core): Extend onnhandledrejection with ignore errors option (#​17736)

    Added support for selectively suppressing specific errors with configurable logging control in onnhandledrejection integration.

Other Changes
  • feat(core): Rename vercelai.schema to gen_ai.request.schema (#​17850)
  • feat(core): Support stream responses and tool calls for Google GenAI (#​17664)
  • feat(nextjs): Attach headers using client hook (#​17831)
  • fix(core): Keep all property values in baggage header (#​17847)
  • fix(nestjs): Add support for Symbol as event name (#​17785)
  • fix(nuxt): include sentry.client.config.ts in nuxt app types (#​17830)
  • fix(react-router): Fix type for OriginalHandleRequest with middleware (#​17870)
Internal Changes
  • chore: Add external contributor to CHANGELOG.md (#​17866)
  • chore(deps): Bump @​sentry/cli from 2.53.0 to 2.56.0 (#​17819)
  • chore(deps): Bump axios in browser integration tests (#​17839)
  • chore(deps): Bump nestjs in integration tests (#​17840)

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

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 [email protected] due to @vercel/nft incompatibility (#​17777)" (#​17784)
  • test(e2e): Pin [email protected] 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)
discordjs/discord.js (discord.js)

v14.23.2

Compare Source

Bug Fixes

v14.23.1

Compare Source

Bug Fixes

v14.23.0

Compare Source

Bug Fixes

Documentation

Features

Refactor

  • ActionsManager: Register actions without using class name (#​11080) (0dff969)

Typings

motdotla/dotenv (dotenv)

v17.2.3

Compare Source

Changed
  • Fixed typescript error definition (#​912)
Automattic/mongoose (mongoose)

v8.19.2

Compare Source

===================

  • perf(setDefaultsOnInsert): avoid computing all modified paths when running setDefaultsOnInsert and update validators, only calculate if there are defaults to set #​15691 #​15672
  • fix: correct handling of relative vs absolute paths with maps and subdocuments #​15682 #​15678 #​15350
  • ci: add publish script with provenance #​15684 #​15680

v8.19.1

Compare Source

===================

  • perf: avoid getting all modified paths in update when checking if versionKey needs to be set #​15677 #​15672
  • perf: Avoid needless path translation #​15679 orgads
  • fix(query): throw error if using update operator with modifier and no path #​15670 #​15642
  • types: avoid making FilterQuery a conditional type because of how typescript handles distributed conditional unions #​15676 #​15671
  • docs: update installation instructions #​15675 aalok-y

v8.19.0

Compare Source

===================

v8.18.3

Compare Source

===================

v8.18.2

Compare Source

===================

  • fix(document): prevent $clone() from converting mongoose arrays into vanilla arrays #​15633 #​15625
  • fix(connection): use correct collection name for model when using useConnection() #​15637
  • fix(connection): propagate changes to _lastHeartbeatAt to useDb() child connections #​15640 #​15635
  • types: fix schema property type definition in SchemaType #​15631
microsoft/TypeScript (typescript)

v5.9.3: TypeScript 5.9.3

Compare Source

Note: this tag was recreated to point at the correct commit. The npm package contained the correct content.

For release notes, check out the release announcement

Downloads are available on:


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.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


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

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot changed the title chore(deps): update dependency @types/node to v24.3.3 chore(deps): update dependency @types/node to v24.4.0 Sep 14, 2025
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 58093c1 to 8871982 Compare September 14, 2025 12:22
@renovate renovate bot changed the title chore(deps): update dependency @types/node to v24.4.0 chore(deps): update dependency @types/node to v24.5.0 Sep 15, 2025
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from 5e10347 to 9153884 Compare September 16, 2025 18:58
@renovate renovate bot changed the title chore(deps): update dependency @types/node to v24.5.0 chore(deps): update all non-major dependencies Sep 16, 2025
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 4 times, most recently from 3ad4f91 to c4fb235 Compare September 23, 2025 09:53
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 8 times, most recently from 5edf732 to b6f6075 Compare October 1, 2025 03:23
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 7 times, most recently from 9af8891 to 3609c52 Compare October 9, 2025 01:49
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 4 times, most recently from a0537f0 to 3dbb37c Compare October 16, 2025 13:14
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 3dbb37c to 9e473cd Compare October 17, 2025 04:37
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from 79be088 to 75e5a80 Compare October 20, 2025 22:29
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 75e5a80 to 1ae82e3 Compare October 21, 2025 01:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants