build(deps): bump @sentry/node from 10.46.0 to 10.47.0

[dependabot]

Bumps @sentry/node from 10.46.0 to 10.47.0.

Release notes

Sourced from @​sentry/node's releases.

10.47.0

Important Changes

• feat(node-core): Add OTLP integration for node-core/light (#19729)

  Added otlpIntegration at @sentry/node-core/light/otlp for users who manage their own OpenTelemetry setup and want to send trace data to Sentry without adopting the full @sentry/node SDK.

  import { NodeTracerProvider } from '@opentelemetry/sdk-trace-node';
  import * as Sentry from '@sentry/node-core/light';
  import { otlpIntegration } from '@sentry/node-core/light/otlp';
  const provider = new NodeTracerProvider();
  provider.register();
  Sentry.init({
  dsn: 'DSN',
  integrations: [
  otlpIntegration({
  // Export OTel spans to Sentry via OTLP (default: true)
  setupOtlpTracesExporter: true,
  }),
  ],
  });

  The integration links Sentry errors to OTel traces and exports spans to Sentry via OTLP.

• feat(node, bun): Add runtime metrics integrations for Node.js and Bun (#19923, #19979)

  New nodeRuntimeMetricsIntegration and bunRuntimeMetricsIntegration automatically collect runtime health metrics and send them to Sentry on a configurable interval (default: 30s). Collected metrics include memory (RSS, heap used/total), CPU utilization, event loop utilization, and process uptime. Node additionally collects event loop delay percentiles (p50, p99). Extra metrics like CPU time and external memory are available as opt-in.

  // Node.js
  import * as Sentry from '@sentry/node';
  Sentry.init({
  dsn: '...',
  integrations: [Sentry.nodeRuntimeMetricsIntegration()],
  });
  // Bun
  import * as Sentry from '@​sentry/bun';
  Sentry.init({
  dsn: '...',
  integrations: [Sentry.bunRuntimeMetricsIntegration()],
  });

... (truncated)

Changelog

Sourced from @​sentry/node's changelog.

10.47.0

Important Changes

• feat(node-core): Add OTLP integration for node-core/light (#19729)

  Added otlpIntegration at @sentry/node-core/light/otlp for users who manage their own OpenTelemetry setup and want to send trace data to Sentry without adopting the full @sentry/node SDK.

  import { NodeTracerProvider } from '@opentelemetry/sdk-trace-node';
  import * as Sentry from '@sentry/node-core/light';
  import { otlpIntegration } from '@sentry/node-core/light/otlp';
  const provider = new NodeTracerProvider();
  provider.register();
  Sentry.init({
  dsn: 'DSN',
  integrations: [
  otlpIntegration({
  // Export OTel spans to Sentry via OTLP (default: true)
  setupOtlpTracesExporter: true,
  }),
  ],
  });

  The integration links Sentry errors to OTel traces and exports spans to Sentry via OTLP.

• feat(node, bun): Add runtime metrics integrations for Node.js and Bun (#19923, #19979)

  New nodeRuntimeMetricsIntegration and bunRuntimeMetricsIntegration automatically collect runtime health metrics and send them to Sentry on a configurable interval (default: 30s). Collected metrics include memory (RSS, heap used/total), CPU utilization, event loop utilization, and process uptime. Node additionally collects event loop delay percentiles (p50, p99). Extra metrics like CPU time and external memory are available as opt-in.

  // Node.js
  import * as Sentry from '@sentry/node';
  Sentry.init({
  dsn: '...',
  integrations: [Sentry.nodeRuntimeMetricsIntegration()],
  });
  // Bun
  import * as Sentry from '@​sentry/bun';
  Sentry.init({
  dsn: '...',
  integrations: [Sentry.bunRuntimeMetricsIntegration()],

... (truncated)

Commits

• a5a4e73 release: 10.47.0
• c7477bb Merge pull request #20050 from getsentry/prepare-release/10.47.0
• 3d4e38d meta(changelog): Update changelog for 10.47.0
• 2c0ce6f feat(deps): Bump OpenTelemetry dependencies (#20046)
• 8f08fcb fix(browser-tests): Pin axios to 1.13.5 to avoid compromised 1.14.1 (#20047)
• 3815492 fix(profiling): Disable profiling in worker threads (#20040)
• 61edc25 Merge pull request #19890 from getsentry/fix/react-router-debug-id-double-inj...
• 28f94f3 fix(react-router): Disable debug ID injection in Vite plugin to prevent doubl...
• 9bfc682 ref(browser-tests): Add waitForMetricRequest helper (#20002)
• 08cab24 fix(node): Deduplicate sentry-trace and baggage headers on outgoing reque...
• 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 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)

---

Note

Bump @sentry/node from 10.46.0 to 10.47.0

Updates the @sentry/node dependency range in package.json and regenerates the lockfile to reflect the new resolution.

^{Macroscope summarized b30be10.}

[greptile-apps]

Greptile Summary

This is a routine Dependabot minor-version bump of @sentry/node from 10.46.0 to 10.47.0. The lockfile updates follow naturally, pulling in compatible transitive bumps for @opentelemetry/api (1.9.0 → 1.9.1), @opentelemetry/api-logs (0.213.0 → 0.214.0), @fastify/otel (0.17.1 → 0.18.0), and several @aws-sdk packages.

Key highlights from the 10.47.0 release:

• New: nodeRuntimeMetricsIntegration — automatic collection of memory, CPU, and event-loop metrics (opt-in; no behaviour change unless explicitly wired in).
• New: otlpIntegration for @sentry/node-core/light — relevant only for custom OTel setups.
• Fix: Profiling disabled in worker threads (prevents crashes in multi-threaded workloads).
• Fix: Deduplication of sentry-trace / baggage headers on outgoing requests.

No breaking changes are listed in the release notes. The new features are all additive and opt-in, so existing Sentry initialisation code is unaffected.

Confidence Score: 5/5

Safe to merge — additive minor version bump with no breaking changes and several bug fixes.

All changes are auto-generated by Dependabot for a minor semver bump. The release notes confirm no breaking changes; new features are opt-in. Transitive dependency updates (OTel 1.9.1, AWS SDK patches) are all patch/minor within compatible ranges. No application code was touched.

No files require special attention.

Important Files Changed

Filename	Overview
package.json	Single-line version bump of @sentry/node from ^10.46.0 to ^10.47.0; no other changes.
pnpm-lock.yaml	Lockfile updated for @sentry/node 10.47.0, with cascading transitive bumps: @opentelemetry/api 1.9.0→1.9.1, @opentelemetry/api-logs 0.213.0→0.214.0, @fastify/otel 0.17.1→0.18.0, several @aws-sdk packages, and @wopr-network/* peer-dependency hash changes. All changes appear consistent and auto-generated.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A["@sentry/node 10.46.0"] -->|"Dependabot bump"| B["@sentry/node 10.47.0"]
    B --> C["@opentelemetry/api 1.9.0 → 1.9.1"]
    B --> D["@opentelemetry/api-logs 0.213.0 → 0.214.0"]
    B --> E["@fastify/otel 0.17.1 → 0.18.0"]
    B --> F["@aws-sdk/* patches"]
    B --> G["New opt-in features\nnodeRuntimeMetricsIntegration\notlpIntegration"]
    B --> H["Bug fixes\nprofiling in worker threads\nheader deduplication"]

Loading

_{Reviews (1): Last reviewed commit: "build(deps): bump @sentry/node from 10.4..." | Re-trigger Greptile}

[TSavo]

Closing — wopr-platform is in the platform monorepo now.

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.