Skip to content

chore(deps): bump @opentelemetry/core and @sentry/electron - #6279

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/multi-6691fbf3fa
Open

chore(deps): bump @opentelemetry/core and @sentry/electron#6279
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/multi-6691fbf3fa

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Jul 24, 2026

Copy link
Copy Markdown
Contributor

Bumps @opentelemetry/core to 2.10.0 and updates ancestor dependency @sentry/electron. These dependencies need to be updated together.

Updates @opentelemetry/core from 2.5.0 to 2.10.0

Release notes

Sourced from @​opentelemetry/core's releases.

v2.10.0

2.10.0

🚀 Features

  • feat(sdk-logs): implement log processor metrics #6554 @​anuraaga
  • feat(otlp-exporter): implement exporter metrics #6480 @​anuraaga
  • feat(propagator-jaeger): Notice: The @opentelemetry/propagator-jaeger package will be removed in SDK 3.x, planned for approximately September 2026. @​pichlermarc
    • The Jaeger propagator has been deprecated by the OpenTelemetry specification in favor of W3CTraceContextPropagator. This package will be removed in a future release.

🐛 Bug Fixes

  • fix(sdk-trace): reject SimpleSpanProcessor.forceFlush() when a pending export fails #6771 @​LarryHu0217
  • fix(sdk-trace): include trace IDs at the ratio 1 upper bound in TraceIdRatioBasedSampler #6890 @​LarryHu0217

🏠 Internal

v2.9.0

2.9.0

💥 Breaking Changes

  • docs(shim-opentracing): Notice: The @opentelemetry/shim-opentracing package will be removed in SDK 3.x, planned for approximately September 2026.
    • The OpenCensus and OpenTracing compatibility requirements in the OpenTelemetry specification have been deprecated.

🚀 Features

  • feat(sdk-metrics): add maxExportBatchSize option to PeriodicExportingMetricReader #6655 @​psx95
    • Optimized PeriodicExportingMetricReader.forceFlush to prevent redundant concurrent export cycles. Concurrent calls to forceFlush will now await any ongoing export and reuse a fresh export cycle if one is started concurrently by another caller. This ensures the latest metrics are always exported efficiently without triggering duplicate collection and export cycles.
  • feat(sdk-trace): implement span processor metrics #6504 @​anuraaga
  • feat(sdk-trace): add a new "sdk-trace" package to hold the Trace SDK, without environment variable configuration handling that belongs elsewhere #6775 @​trentm
    • "sdk-trace" will eventually replace all of "sdk-trace-base", "sdk-trace-node", and "sdk-trace-web".
    • The BatchSpanProcessor constructor call signature has changed in "sdk-trace". For example, before new BatchSpanProcessor(exporter, { maxQueueSize: 1000 }), after new BatchSpanProcessor({ exporter, maxQueueSize: 1000 }). #6817
    • The SimpleSpanProcessor constructor call signature has changed in "sdk-trace". For example, before new SimpleSpanProcessor(exporter), after new SimpleSpanProcessor({ exporter, selfObsMeterProvider: ... }). #6504
  • feat(sdk-trace): add AlwaysRecordSampler #6188 @​majanjua-amzn

🐛 Bug Fixes

  • fix(propagator-jaeger): do not throw on malformed percent-encoded uber-trace-id / uberctx-* headers during extract @​pichlermarc

🏠 Internal

  • perf(sdk-metrics): defer allocation of HrTime to accumulation creation #6839 @​legendecas
  • chore(*): migrate use of sdk-trace-base and sdk-trace-node to sdk-trace #6851 @​trentm
  • perf(sdk-metrics): optionally capture active context for sync instruments #6848 @​legendecas

... (truncated)

Changelog

Sourced from @​opentelemetry/core's changelog.

2.10.0

🚀 Features

  • feat(sdk-logs): implement log processor metrics #6554 @​anuraaga
  • feat(otlp-exporter): implement exporter metrics #6480 @​anuraaga
  • feat(propagator-jaeger): Notice: The @opentelemetry/propagator-jaeger package will be removed in SDK 3.x, planned for approximately September 2026. @​pichlermarc
    • The Jaeger propagator has been deprecated by the OpenTelemetry specification in favor of W3CTraceContextPropagator. This package will be removed in a future release.

🐛 Bug Fixes

  • fix(sdk-trace): reject SimpleSpanProcessor.forceFlush() when a pending export fails #6771 @​LarryHu0217
  • fix(sdk-trace): include trace IDs at the ratio 1 upper bound in TraceIdRatioBasedSampler #6890 @​LarryHu0217

🏠 Internal

2.9.0

💥 Breaking Changes

  • docs(shim-opentracing): Notice: The @opentelemetry/shim-opentracing package will be removed in SDK 3.x, planned for approximately September 2026.
    • The OpenCensus and OpenTracing compatibility requirements in the OpenTelemetry specification have been deprecated.

🚀 Features

  • feat(sdk-metrics): add maxExportBatchSize option to PeriodicExportingMetricReader #6655 @​psx95
    • Optimized PeriodicExportingMetricReader.forceFlush to prevent redundant concurrent export cycles. Concurrent calls to forceFlush will now await any ongoing export and reuse a fresh export cycle if one is started concurrently by another caller. This ensures the latest metrics are always exported efficiently without triggering duplicate collection and export cycles.
  • feat(sdk-trace): implement span processor metrics #6504 @​anuraaga
  • feat(sdk-trace): add a new "sdk-trace" package to hold the Trace SDK, without environment variable configuration handling that belongs elsewhere #6775 @​trentm
    • "sdk-trace" will eventually replace all of "sdk-trace-base", "sdk-trace-node", and "sdk-trace-web".
    • The BatchSpanProcessor constructor call signature has changed in "sdk-trace". For example, before new BatchSpanProcessor(exporter, { maxQueueSize: 1000 }), after new BatchSpanProcessor({ exporter, maxQueueSize: 1000 }). #6817
    • The SimpleSpanProcessor constructor call signature has changed in "sdk-trace". For example, before new SimpleSpanProcessor(exporter), after new SimpleSpanProcessor({ exporter, selfObsMeterProvider: ... }). #6504
  • feat(sdk-trace): add AlwaysRecordSampler #6188 @​majanjua-amzn

🐛 Bug Fixes

  • fix(propagator-jaeger): do not throw on malformed percent-encoded uber-trace-id / uberctx-* headers during extract @​pichlermarc

🏠 Internal

  • perf(sdk-metrics): defer allocation of HrTime to accumulation creation #6839 @​legendecas
  • chore(*): migrate use of sdk-trace-base and sdk-trace-node to sdk-trace #6851 @​trentm
  • perf(sdk-metrics): optionally capture active context for sync instruments #6848 @​legendecas

2.8.0

🚀 Features

... (truncated)

Commits
  • 76fa6b5 chore: prepare next release (#6942)
  • 3787896 chore(deps): update dependency webpack-cli to v7.2.1 (#6934)
  • be5f757 fix(deps): update dependency body-parser to v2.3.0 [security] (#6941)
  • f6d8fbe chore(deps): lock file maintenance (#6559)
  • 9612732 chore: remove examples/dice from workspaces (#6937)
  • 7107906 chore: start using min-release-age in .npmrc, disable minimumReleaseAge for r...
  • a7e5d11 chore(deps): update dependency webpack to v5.108.4 (#6933)
  • af7a82d chore(deps): update dependency msw to v2.15.0 (#6831)
  • b9f57c6 chore(deps): update dependency @​types/webpack-env to v1.18.8 (#6877)
  • cbb4abf chore(deps): update ubuntu docker tag to v26 (#6635)
  • Additional commits viewable in compare view

Updates @sentry/electron from 7.8.0 to 7.16.0

Release notes

Sourced from @​sentry/electron's releases.

7.16.0

New Features ✨

Internal Changes 🔧

Deps

Other

7.15.0

New Features ✨

Bug Fixes 🐛

Internal Changes 🔧

7.14.0

New Features ✨

Bug Fixes 🐛

  • (net) Propagate correct distributed tracing IDs by @​lcian in #1389

Internal Changes 🔧

... (truncated)

Changelog

Sourced from @​sentry/electron's changelog.

7.16.0

New Features ✨

Internal Changes 🔧

Deps

Other

7.15.0

New Features ✨

Bug Fixes 🐛

Internal Changes 🔧

7.14.0

New Features ✨

Bug Fixes 🐛

... (truncated)

Commits


Note

Medium Risk
Changes Electron crash/error reporting and Node-side instrumentation without source edits; version skew between @sentry/react and the Electron SDK’s nested Sentry 10.67 packages warrants smoke-testing desktop builds and Sentry events.

Overview
Bumps @sentry/electron from 7.8.0 to 7.16.0 in package.json, with the matching package-lock.json refresh. There are no application code changes.

The new Electron SDK pulls in Sentry JavaScript 10.67 for its main-process stack (@sentry/node, @sentry/browser, @sentry/core), while the direct @sentry/react dependency stays on 10.39.0, so renderer and Electron paths may run different Sentry core versions until aligned.

The lockfile also reflects a slimmer @sentry/node dependency tree: many per-framework OpenTelemetry instrumentation packages are dropped in favor of @sentry/server-utils and updated OpenTelemetry pieces (@opentelemetry/core 2.10.0, import-in-the-middle v3, etc.).

Reviewed by Cursor Bugbot for commit 87980b9. Bugbot is set up for automated code reviews on this repo. Configure here.

@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Jul 24, 2026
@dependabot
dependabot Bot requested a review from a team as a code owner July 24, 2026 05:18
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Jul 24, 2026

@cursor cursor Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.

Fix All in Cursor

❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.

Reviewed by Cursor Bugbot for commit d203b47. Configure here.

Comment thread package.json Outdated
"@redis-ui/table": "^3.7.0",
"@reduxjs/toolkit": "^2.12.0",
"@sentry/electron": "^7.8.0",
"@sentry/electron": "^7.15.0",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Dual @sentry/core versions cause SDK state split

Medium Severity

Bumping @sentry/electron to 7.15.0 (which depends on @sentry/core@10.62.0) without also bumping @sentry/react (still at 10.39.0, using @sentry/core@10.39.0) creates two copies of @sentry/core in the dependency tree. In sentryElectron.ts, @sentry/electron/renderer (core 10.62.0) and reactInit from @sentry/react (core 10.39.0) are used together in Sentry.init(…, reactInit). These two SDK instances may not properly share the global Sentry hub/scope/client state, potentially causing events to be silently dropped or misconfigured.

Additional Locations (1)
Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit d203b47. Configure here.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: d203b473ef

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

Comment thread package.json Outdated
"@redis-ui/table": "^3.7.0",
"@reduxjs/toolkit": "^2.12.0",
"@sentry/electron": "^7.8.0",
"@sentry/electron": "^7.15.0",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Keep Sentry packages on one SDK version

In the Electron renderer, redisinsight/ui/src/services/sentryElectron.ts initializes @sentry/electron/renderer with reactInit from @sentry/react, but this bump installs Electron’s bundled Sentry JS SDKs at 10.62.0 while the direct @sentry/react dependency stays on 10.39.0 (package-lock.json shows both versions). When Sentry is enabled in the Electron renderer this combines two different Sentry core/browser versions, which can break the framework init/capture path; please bump @sentry/react to the matching 10.62.x version with this change.

Useful? React with 👍 / 👎.

Bumps [@opentelemetry/core](https://github.com/open-telemetry/opentelemetry-js) to 2.10.0 and updates ancestor dependency [@sentry/electron](https://github.com/getsentry/sentry-electron). These dependencies need to be updated together.


Updates `@opentelemetry/core` from 2.5.0 to 2.10.0
- [Release notes](https://github.com/open-telemetry/opentelemetry-js/releases)
- [Changelog](https://github.com/open-telemetry/opentelemetry-js/blob/main/CHANGELOG.md)
- [Commits](open-telemetry/opentelemetry-js@v2.5.0...v2.10.0)

Updates `@sentry/electron` from 7.8.0 to 7.16.0
- [Release notes](https://github.com/getsentry/sentry-electron/releases)
- [Changelog](https://github.com/getsentry/sentry-electron/blob/master/CHANGELOG.md)
- [Commits](getsentry/sentry-electron@7.8.0...7.16.0)

---
updated-dependencies:
- dependency-name: "@opentelemetry/core"
  dependency-version: 2.10.0
  dependency-type: indirect
- dependency-name: "@sentry/electron"
  dependency-version: 7.15.0
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot
dependabot Bot force-pushed the dependabot/npm_and_yarn/multi-6691fbf3fa branch from d203b47 to 87980b9 Compare July 29, 2026 12:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants