[Snyk] Upgrade @opentelemetry/sdk-logs from 0.209.0 to 0.213.0

[Mpdreamz]

Snyk has created this PR to upgrade @opentelemetry/sdk-logs from 0.209.0 to 0.213.0.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

---

• The recommended version is 4 versions ahead of your current version.

• The recommended version was released a month ago.

Breaking Change Risk

Notice: This assessment is enhanced by AI.

Release notes

Package name: @opentelemetry/sdk-logs

• 0.213.0 - 2026-03-03
  

  0.213.0

  💥 Breaking Changes

  • fix(api-logs)!: drop lingering includeTraceContext from LoggerOptions type #6451 @ trentm

  🚀 Features

  • feat(instrumentation-http): provide http.request.header.<key> at server span creation time #6396 @ vitorvasc

  🐛 Bug Fixes

  • fix(instrumentation-http): guard against double-instrumentation if loaded with require('http') and import 'http' #6428 @ trentm
  • fix(otlp-exporter-base): handle response error #6412 @ pichlermarc
    • Fixes a bug where when the response header was received, but the connection was reset by the server,
      an unhandled error would be thrown.
  • fix(otlp-exporter-base): remove sendBeacon in favor of fetch with keepalive #6391 @ overbalance
    • (user-facing) createOtlpSendBeaconExportDelegate will be removed in a future version
  • fix(otlp-transformer): downgrade protobufjs to version ^7.0.0 #6418 @ vitorvasc
  • fix(instrumentation-fetch): handle HeadersInit tuple arrays in _addHeaders #6341 @ overbalance @ imadha
• 0.212.0 - 2026-02-12
  

  0.212.0

  💥 Breaking Changes

  • feat(sdk-logs)!: move environment variable configuration to @ opentelemetry/sdk-node #6325 @ pichlermarc
    • (user-facing): environment variable configuration is no longer applied automatically when instantiating SDK components
      (LoggerProvider, BatchLogRecordProcessor) directly from @ opentelemetry/sdk-logs. Please migrate to using
      NodeSDK from @ opentelemetry/sdk-node to get automatic environment variable configuration.

  🚀 Features

  • feat(configuration): add Prometheus exporter support #6400 @ MikeGoldsmith
  • feat(sampler-composite): add ComposableAnnotatingSampler and ComposableRuleBasedSampler #6305 @ trentm
  • feat(configuration): parse config for rc 3 #6304 @ maryliag
  • feat(instrumentation): use the internals: true option with import-in-the-middle hook, allowing instrumentations to hook internal files in ES modules #6344 @ trentm

  🐛 Bug Fixes

  • fix(configuration): remove default propagator initialization #6399 @ MikeGoldsmith
  • fix(instrumentation-fetch): preserve Response.url, type, and redirected properties #6243 @ AnubhavPurohit691
    • The fetch instrumentation now preserves the read-only url, type, and redirected properties from the original Response object when wrapping it with a Proxy. This fixes issues where code relying on these properties (e.g., CORS type detection) would fail with instrumented fetch.
  • fix(exporter-prometheus): add missing @ opentelemetry/semantic-conventions dependency #6330 @ omizha
  • fix(otlp-transformer): correctly handle Uint8Array attribute values when serializing to JSON #6348 @ pichlermarc
  • fix(otlp-exporter-base): fix unwanted instrumentation of the fetch exports when context is not propagated #6353 @ david-luna

  🏠 Internal

  • perf(otlp-transformer): optimize toAnyValue performance #6287 @ AbhiPrasad
• 0.211.0 - 2026-01-21
  

  0.211.0

  💥 Breaking Changes

  • fix(otlp-exporter-base)!: remove xhr transport #6317 @ cjihrig
    • (user-facing) The deprecated XHR-based transport has been removed and replaced with fetch(). This change affects users who relied on XmlHttpRequest instead of fetch() for sending headers with OTLP exports. To maintain compatibility on browsers without a fetch() implementation, include a fetch() polyfill.
  • chore(api-logs)!: remove ProxyLoggerProvider export #6322 @ david-luna

  🚀 Features

  • feat(sdk-logs): export event name from ConsoleLogRecordExporter #6310 @ aicest

  🐛 Bug Fixes

  • fix(sdk-logs): allow AnyValue attributes for logs and handle circular references #6210 @ david-luna
    • based on #5765 from @ Alec2435
  • fix(browser-detector): use window feature detection to avoid false positives in Node.js 21+ and Bun #6271 @ fiyinfoluwa001 @ overbalance

  🏠 Internal

  • fix(build): update @ types/node to 18.19.130, remove DOM types from base tsconfig #6280 @ overbalance
  • refactor(sdk-logs): simplify _export() #6318 @ cjihrig
• 0.210.0 - 2026-01-14
• 0.209.0 - 2026-01-08

from @opentelemetry/sdk-logs GitHub release notes

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• This PR was automatically created by Snyk using the credentials of a real user.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

• 🧐 View latest project report
• 📜 Customise PR templates
• 🛠 Adjust upgrade PR settings
• 🔕 Ignore this dependency or unsubscribe from future upgrade PRs

[Mpdreamz]

This upgrade contains significant breaking changes that require developer action. The package is experimental, and minor versions may introduce breaking changes.

Key Breaking Changes:

• Environment Variable Configuration (v0.212.0): Automatic configuration from environment variables (e.g., OTEL_*) is no longer applied when creating a LoggerProvider or BatchLogRecordProcessor directly from @opentelemetry/sdk-logs. This can cause your logging configuration to be silently ignored.
• API Option Removal (v0.213.0): The includeTraceContext property has been removed from the LoggerOptions type in the corresponding @opentelemetry/api-logs package.

Recommendation:
To ensure your logging configuration is still applied correctly, you must migrate your application's initialization code to use the NodeSDK from the @opentelemetry/sdk-node package, which now handles the automatic environment variable configuration.

Source: OpenTelemetry-JS Release Notes

Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.

[github-actions]

Label error. Requires exactly 1 of: automation, breaking, bug, changelog:skip, chore, ci, dependencies, documentation, enhancement, feature, fix, redesign. Found: