Bump @opentelemetry/instrumentation from 0.211.0 to 0.212.0

[dependabot]

Bumps @opentelemetry/instrumentation from 0.211.0 to 0.212.0.

Release notes

Sourced from @​opentelemetry/instrumentation's releases.

experimental/v0.212.0

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

Commits

• ad92be4 chore: prepare next release (#6402)
• 3e68499 feat(configuration): add prometheus exporter support (#6400)
• b743747 fix(configuration): remove default propagator initialization (#6399)
• 48e2fb4 chore(deps): update fossas/fossa-action action to v1.8.0 (#6405)
• 90d1afa ci: allow different release bumps for groups (#6397)
• c1d0543 fix(deps): update dependency axios to v1.13.5 [security] (#6398)
• a78d112 fix(deps): update dependency @​grpc/grpc-js to v1.8.22 [security] (#6366)
• fcafab5 chore: fix lint (#6388)
• a0d5c14 fix(otlp-exporter-base): avoid use of a wrapped fetch (#6353)
• 819ebb2 chore(deps): update dependency webpack-merge to v6 (#6364)
• 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)

[github-actions]

vet Summary Report

This report is generated by vet

Policy Checks

• ✅ Vulnerability
• ✅ Malware
• ✅ License
• ✅ Popularity
• ✅ Maintenance
• ✅ Security Posture
• ✅ Threats

Malicious Package Analysis

Active malicious package analysis was disabled. Learn more about enabling active package analysis

Malicious Package Analysis Report

Ecosystem	Package	Version	Status	Report
ECOSYSTEM_NPM	@opentelemetry/instrumentation	0.212.0	✅	🔗

• ℹ️ 1 packages have been actively analyzed for malicious behaviour.
• ✅ No malicious packages found.

Note: Only known malicious packages were reported. Consider enabling active package analysis to get more accurate results.

Changed Packages

Changed Packages

• ✅ [Npm] @opentelemetry/instrumentation@0.212.0
• ✅ [Npm] @opentelemetry/api-logs@0.212.0

[dependabot]

Looks like @opentelemetry/instrumentation is no longer updatable, so this is no longer needed.