[Snyk] Upgrade @opentelemetry/sdk-logs from 0.216.0 to 0.217.0

[reakaleek]

Snyk has created this PR to upgrade @opentelemetry/sdk-logs from 0.216.0 to 0.217.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 1 version 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.217.0 - 2026-05-06
  

  0.217.0

  🚀 Features

  • feat(otlp-transformer): replace protobufjs trace serialization with custom implementation #6625 @ pichlermarc
  • feat(configuration): auto-generate TypeScript types from OTel declarative config JSON schema (stable v1.0.0) using json-schema-to-typescript and ajv #6533 @ MikeGoldsmith
  • feat(configuration, sdk-node): startNodeSDK() code path now uses log_level configuration to setup a DiagConsoleLogger #6668 @ trentm
    • Note that allowed values for log_level in a configuration YAML file are not the same set as for OTEL_LOG_LEVEL. Use log_level: trace to see all logs (equivalent of OTEL_LOG_LEVEL=ALL). Use log_level: fatal to effectively disable the SDK's internal diagnostic logger (equivalent of OTEL_LOG_LEVEL=NONE).
    • If log_level is not specified, a diagnostic console logger at "info" level will be setup.
    • An invalid YAML config file will now result in a noop OTel SDK.

  🐛 Bug Fixes

  • fix(configuration): do not validate OTEL_CONFIG_FILE value before using it for file config #6643 @ trentm
  • fix(configuration): improve how 'additionalProperties' in JSON schema is translated to TS types #6650 @ trentm
  • fix(configuration): remove stripMinItems and preprocessNullArrays from validation/parsing #6657 @ trentm
  • fix(configuration): improve handling of enums in generated types #6659 @ trentm
  • fix(configuration): improve the technique for removing '| null' on types the JSON Schema #6662 @ trentm
  • fix(sampler-jaeger-remote): add missing axios dep #6656 @ trentm
  • fix(exporter-prometheus): handle malformed URLs in Prometheus exporter request handler #6674 @ homanp
• 0.216.0 - 2026-04-29
  

  0.216.0

  🚀 Features

  • feat(sdk-node): wire attribute_keys from declarative configuration to ViewOptions.attributesProcessors #6427 @ ravitheja4531-cell
  • feat(sdk-node): set TracerProvider in startNodeSDK() #6607 @ maryliag

  🐛 Bug Fixes

  • fix(instrumentation-xml-http-request): avoid unwrapping XMLHttpRequest API when disabling #6611 @ david-luna
  • fix(instrumentation-fetch): tolerate non-writable globalThis.fetch and fix premature _isEnabled / _isFetchPatched flips in enable() @ brunorodmoreira
  • fix(instrumentation-xhr): resolve relative URLs before matching ignoreUrls #6551 @ Maximiliano-Zeballos
  • fix(sdk-node): fix setting of ViewOption#name from ConfigurationModel #6620 @ trentm
  • fix(web-common): add limit for timeout #6601 @ maryliag
  • fix(otlp-transformer): pin protobufjs@8.0.1 as protobufjs@8.0.3 is broken for browser use #6646

  🏠 Internal

  • test(otlp-transformer): add metrics transform benchmark #6628 @ pichlermarc
  • refactor(opentelemetry-exporter-prometheus): do not call enforcePrometheusNamingConvention() multiple times per metric #6636 @ cjihrig

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

[reakaleek]

This upgrade to @opentelemetry/sdk-logs introduces a significant breaking change.

Breaking Change:

• The LogRecordExporter interface now requires a forceFlush() method. If you have implemented any custom log exporters, they will fail to compile or run until this method is added.

Recommendation:
Review any custom implementations of LogRecordExporter and add the required forceFlush() method. If you are only using exporters provided by OpenTelemetry, you should not be directly affected, but verification is recommended.

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.