Skip to content

Bump @sentry/react from 10.11.0 to 10.12.0 #834

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
merged 1 commit into from
Sep 17, 2025
Merged

Bump @sentry/react from 10.11.0 to 10.12.0 #834

merged 1 commit into from
Sep 17, 2025

Conversation

@dependabot
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Sep 17, 2025

Bumps @sentry/react from 10.11.0 to 10.12.0.

Release notes

Sourced from @​sentry/react's releases.

10.12.0

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.

    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)

... (truncated)

Changelog

Sourced from @​sentry/react's changelog.

10.12.0

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.

    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)

... (truncated)

Commits
  • a3a070b release: 10.12.0
  • bbafac0 Merge pull request #17670 from getsentry/prepare-release/10.12.0
  • ce1c0a5 meta(changelog): Update changelog for 10.12.0
  • dde442c Merge pull request #17660 from getsentry/prepare-release/10.12.0
  • c076017 meta(changelog): Update changelog for 10.12.0
  • dd17203 fix(core): Fix error handling when sending envelopes (#17662)
  • e8d255f Revert "feat(cloudflare): Introduce lock instrumentation for `context.waitUnt...
  • 57b0656 ref(browser): Improve fetchTransport error handling (#17661)
  • 41cec5b test: Adjust node test runner to avoid timeouts (#17663)
  • 108ed16 test(sveltekit): Pin E2E test app SvelteKit versions and fix failing tests (#...
  • Additional commits viewable in compare view

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

@dependabot
Bump @sentry/react from 10.11.0 to 10.12.0
e109036 
Bumps [@sentry/react](https://github.com/getsentry/sentry-javascript) from 10.11.0 to 10.12.0.
- [Release notes](https://github.com/getsentry/sentry-javascript/releases)
- [Changelog](https://github.com/getsentry/sentry-javascript/blob/develop/CHANGELOG.md)
- [Commits](getsentry/sentry-javascript@10.11.0...10.12.0)

---
updated-dependencies:
- dependency-name: "@sentry/react"
  dependency-version: 10.12.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code labels Sep 17, 2025
@ndittren ndittren merged commit 44b0474 into main Sep 17, 2025
3 checks passed
@dependabot dependabot bot deleted the dependabot/npm_and_yarn/sentry/react-10.12.0 branch September 17, 2025 14:22
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

dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@ndittren