chore(deps): bump @sentry/node from 7.109.0 to 8.7.0

[dependabot]

Bumps @sentry/node from 7.109.0 to 8.7.0.

Release notes

Sourced from @​sentry/node's releases.

8.7.0

Important Changes

• feat(react): Add TanStack Router integration (#12095)

  This release adds instrumentation for TanStack router with a new tanstackRouterBrowserTracingIntegration in the @sentry/react SDK:

  import * as Sentry from '@sentry/react';
  import { createRouter } from '@tanstack/react-router';
  const router = createRouter({
  // Your router options...
  });
  Sentry.init({
  dsn: 'PUBLIC_DSN',
  integrations: [Sentry.tanstackRouterBrowserTracingIntegration(router)],
  tracesSampleRate: 1.0,
  });

Other Changes

• fix(nextjs): Do not hide sourceMappingURL comment on client when nextConfig.productionBrowserSourceMaps: true is set (#12278)

8.6.0

8.6.0 did not release fully, so this 8.7.0 also includes changes from that release.

Important Changes

• feat(metrics): Add timings method to metrics (#12226)

  This introduces a new method, metrics.timing(), which can be used in two ways:

  1. With a numeric value, to simplify creating a distribution metric. This will default to second as unit:

  Sentry.metrics.timing('myMetric', 100);

  2. With a callback, which will wrap the duration of the callback. This can accept a sync or async callback. It will create an inactive span around the callback and at the end emit a metric with the duration of the span in seconds:

  const returnValue = Sentry.metrics.timing('myMetric', measureThisFunction);

... (truncated)

Changelog

Sourced from @​sentry/node's changelog.

8.7.0

Important Changes

• feat(react): Add TanStack Router integration (#12095)

  This release adds instrumentation for TanStack router with a new tanstackRouterBrowserTracingIntegration in the @sentry/react SDK:

  import * as Sentry from '@sentry/react';
  import { createRouter } from '@tanstack/react-router';
  const router = createRouter({
  // Your router options...
  });
  Sentry.init({
  dsn: 'PUBLIC_DSN',
  integrations: [Sentry.tanstackRouterBrowserTracingIntegration(router)],
  tracesSampleRate: 1.0,
  });

Other Changes

• fix(nextjs): Do not hide sourceMappingURL comment on client when nextConfig.productionBrowserSourceMaps: true is set (#12278)

8.6.0

Important Changes

• feat(metrics): Add timings method to metrics (#12226)

  This introduces a new method, metrics.timing(), which can be used in two ways:

  1. With a numeric value, to simplify creating a distribution metric. This will default to second as unit:

  Sentry.metrics.timing('myMetric', 100);

  2. With a callback, which will wrap the duration of the callback. This can accept a sync or async callback. It will create an inactive span around the callback and at the end emit a metric with the duration of the span in seconds:

  const returnValue = Sentry.metrics.timing('myMetric', measureThisFunction);

... (truncated)

Commits

• 41b8f79 release: 8.7.0
• d4aaa3a Merge pull request #12280 from getsentry/prepare-release/8.7.0
• 9b09cb2 Merge branch 'master' into prepare-release/8.7.0
• 4aaaba7 meta: Add Changelog entry for 8.7.0
• d9562b9 fix(nextjs): Do not hide sourceMappingURL comment on client when `nextConfi...
• 0d1093d feat(react): Add TanStack Router integration (#12095)
• bbe7be5 build: Remove @types/rimraf and some rimraf usage (#12276)
• 81e0fd1 build: Bump node to 18.20.3 (#12271)
• 264675d Merge pull request #12272 from getsentry/prepare-release/8.6.00
• bf0a138 test(react): Update react-create-hash-router E2E test (#12262)
• Additional commits viewable in compare view

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)

[pull-request-checklist-buddy]

👨‍💻 Dev Branch checks

• All Code checks are successfully?
• No sensetive data leaked?
• Code works as expected?
• Debug Code removed?
• Code Review approved?

[socket-security]

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/@sentry/node@8.7.0	Transitive: environment, filesystem, network, shell, unsafe	+83	14.5 MB

🚮 Removed packages: npm/@sentry/node@7.109.0

View full report↗︎

[socket-security]

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert	Package	Note	Source
Shell access	npm/@opentelemetry/resources@1.24.1	Module: child_process Location: Package overview	package-lock.json package.json
Shell access	npm/@opentelemetry/resources@1.24.1	Module: child_process Location: Package overview	package-lock.json package.json

View full report↗︎

Next steps

What is shell access?

This module accesses the system shell. Accessing the system shell increases the risk of executing arbitrary code.

Packages should avoid accessing the shell which can reduce portability, and make it easier for malicious shell access to be introduced.

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/foo@1.0.0 or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore npm/@opentelemetry/resources@1.24.1

[dependabot]

Superseded by #2016.