Skip to content

chore:(deps): bump @sentry/react from 7.6.0 to 9.13.0 in /explorer #1260

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.

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

Conversation

dependabot[bot]
Copy link

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

Bumps @sentry/react from 7.6.0 to 9.13.0.

Release notes

Sourced from @​sentry/react's releases.

9.13.0

Important Changes

  • feat(node): Add support for winston logger (#15983)

    Sentry is adding support for structured logging. In this release we've added support for sending logs to Sentry via the winston logger to the Sentry Node SDK (and SDKs that use the Node SDK under the hood like @sentry/nestjs). The Logging APIs in the Sentry SDK are still experimental and subject to change.

    const winston = require('winston');
    const Transport = require('winston-transport');
    const transport = Sentry.createSentryWinstonTransport(Transport);
    const logger = winston.createLogger({
    transports: [transport],
    });

  • feat(core): Add wrapMcpServerWithSentry to instrument MCP servers from @modelcontextprotocol/sdk (#16032)

    The Sentry SDK now supports instrumenting MCP servers from the @modelcontextprotocol/sdk package. Compatible with versions ^1.9.0 of the @modelcontextprotocol/sdk package.

    import { McpServer } from '@modelcontextprotocol/sdk/server/mcp.js';
    // Create an MCP server
    const server = new McpServer({
    name: 'Demo',
    version: '1.0.0',
    });
    // Use the instrumented server in your application
    const instrumentedServer = Sentry.wrapMcpServerWithSentry(server);

  • feat(core): Move console integration into core and add to cloudflare/vercel-edge (#16024)

    Console instrumentation has been added to @sentry/cloudflare and @sentry/nextjs Edge Runtime and is enabled by default. Now calls to the console object will be captured as breadcrumbs for those SDKs.

  • feat(bun): Support new Bun.serve APIs (#16035)

    Bun 1.2.6 and above have a new Bun.serve API, which the Bun SDK now supports. The SDK instruments the new routes object that can be used to define routes for the server.

    Thanks to @​Jarred-Sumner for helping us get this supported!

Other Changes

  • feat(browser): Warn on duplicate browserTracingIntegration (#16042)
  • feat(core): Allow delayed sending with offline transport (#15937)
  • feat(deps): Bump @​sentry/webpack-plugin from 3.2.4 to 3.3.1 (#16057)

... (truncated)

Changelog

Sourced from @​sentry/react's changelog.

9.13.0

Important Changes

  • feat(node): Add support for winston logger (#15983)

    Sentry is adding support for structured logging. In this release we've added support for sending logs to Sentry via the winston logger to the Sentry Node SDK (and SDKs that use the Node SDK under the hood like @sentry/nestjs). The Logging APIs in the Sentry SDK are still experimental and subject to change.

    const winston = require('winston');
    const Transport = require('winston-transport');
    const transport = Sentry.createSentryWinstonTransport(Transport);
    const logger = winston.createLogger({
    transports: [transport],
    });

  • feat(core): Add wrapMcpServerWithSentry to instrument MCP servers from @modelcontextprotocol/sdk (#16032)

    The Sentry SDK now supports instrumenting MCP servers from the @modelcontextprotocol/sdk package. Compatible with versions ^1.9.0 of the @modelcontextprotocol/sdk package.

    import { McpServer } from '@modelcontextprotocol/sdk/server/mcp.js';
    // Create an MCP server
    const server = new McpServer({
    name: 'Demo',
    version: '1.0.0',
    });
    // Use the instrumented server in your application
    const instrumentedServer = Sentry.wrapMcpServerWithSentry(server);

  • feat(core): Move console integration into core and add to cloudflare/vercel-edge (#16024)

    Console instrumentation has been added to @sentry/cloudflare and @sentry/nextjs Edge Runtime and is enabled by default. Now calls to the console object will be captured as breadcrumbs for those SDKs.

  • feat(bun): Support new Bun.serve APIs (#16035)

    Bun 1.2.6 and above have a new Bun.serve API, which the Bun SDK now supports. The SDK instruments the new routes object that can be used to define routes for the server.

    Thanks to @​Jarred-Sumner for helping us get this supported!

Other Changes

  • feat(browser): Warn on duplicate browserTracingIntegration (#16042)
  • feat(core): Allow delayed sending with offline transport (#15937)

... (truncated)

Commits
  • 6e775c6 release: 9.13.0
  • 6c1d069 Merge pull request #16078 from getsentry/prepare-release/9.13.0
  • b839506 meta(changelog): Update changelog for 9.13.0
  • 55cb92c chore(dev-deps): Bump amqlib for node-integration-tests to 0.10.7 (#16074)
  • f4cc3d2 fix(serverless-aws): Overwrite root span name with GraphQL if set (#16010)
  • 6a3e7c1 ci: Update label automation to new package label style (#16053)
  • 36be635 fix(nextjs): Don't show turbopack warning for newer Next.js canaries (#16065)
  • d34e67e feat(deps): Bump @​sentry/webpack-plugin from 3.2.4 to 3.3.1 (#16057)
  • 217ac8d build(deps): Bump @​nestjs/common from 10.4.6 to 11.0.16 in /dev-packages/node...
  • cff47df feat(node): Add support for winston logger (#15983)
  • 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)

Bumps [@sentry/react](https://github.com/getsentry/sentry-javascript) from 7.6.0 to 9.13.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@7.6.0...9.13.0)

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

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot @github
Copy link
Author

dependabot bot commented on behalf of github Apr 17, 2025

Labels

The following labels could not be found: automerge. Please create it before Dependabot can add it to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

Copy link
Author

dependabot bot commented on behalf of github Apr 24, 2025

Superseded by #1264.

@dependabot dependabot bot closed this Apr 24, 2025
@dependabot dependabot bot deleted the dependabot/npm_and_yarn/explorer/sentry/react-9.13.0 branch April 24, 2025 08:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants