[dependabot]

Bumps @opentelemetry/exporter-trace-otlp-http from 0.223.0 to 0.300.0.

Release notes

Sourced from @​opentelemetry/exporter-trace-otlp-http's releases.

experimental/v0.300.0

0.300.0

Summary

• The minimum supported Node.js has been raised to >=22.15.0. This means that support for Node.js 18 and 20 has been dropped.
• The public interface has changed
  • for notes on migrating to 3.x / 0.300.x see the upgrade guide
• Only stable versions 3.0.0 are compatible with this release

💥 Breaking Changes

• chore(shim-opencensus)!: remove the @opentelemetry/shim-opencensus package
  • In the OpenTelemetry Specification v1.58.0 the OpenCensus compatibility requirements were deprecated. The JavaScript OpenCensus shim package will not receive any more releases after the current 0.222.0 release (source code for last release).
• feat(instrumentation-http)!: remove deprecated serverName field from HttpInstrumentationConfig #7081
  • The serverName option had no effect; stable HTTP semantic conventions do not include http.server_name. Remove it from any setConfig() or constructor call.
• feat(sdk-node)!: remove deprecated NodeSDKConfiguration fields logRecordProcessor, metricReader, spanProcessor and deprecated namespace re-exports node, tracing
  • NodeSDKConfiguration.logRecordProcessor — use logRecordProcessors instead.
  • NodeSDKConfiguration.metricReader — use metricReaders instead.
  • NodeSDKConfiguration.spanProcessor — use spanProcessors instead.
  • export * as node from '@opentelemetry/sdk-node' — import directly from @opentelemetry/sdk-trace-node instead.
  • export * as tracing from '@opentelemetry/sdk-node' — import directly from @opentelemetry/sdk-trace-base instead.
• feat(sdk-logs)!: remove deprecated SdkLogRecord type alias and LoggerProviderConfig type alias #7062
  • SdkLogRecord — use ReadWriteLogRecord instead.
  • LoggerProviderConfig — use LoggerProviderOptions instead.
• feat!: migrate package builds from tsc to tsdown, emitting dual CJS/ESM output from a single dist/ directory and declaring an exports map on every package #6293 @​overbalance
  • Importing a package by its name is unaffected in both CommonJS and ESM, as is every subpath listed in its exports map.
  • Deep imports into the build output no longer resolve. An exports map is an allowlist that Node.js and bundlers enforce, so specifiers such as @opentelemetry/sdk-logs/build/src/... or @opentelemetry/sdk-logs/build/esm/... now fail with ERR_PACKAGE_PATH_NOT_EXPORTED. Rewriting them to the new file layout does not help — unlisted subpaths are rejected whether or not the file exists.
  • The emitted files moved out of build/src (CJS), build/esm and build/esnext (ESM) into dist/, using .cjs/.mjs extensions with matching .d.cts/.d.mts declarations.
  • <package>/package.json is no longer importable for the same reason. Read a package's version from your own dependency metadata, or use SDK_INFO from @opentelemetry/core for the SDK version.
  • The non-standard esnext entry point has been removed; tools that preferred it fall back to module (ESM) or main (CJS).
  • Packages that ship separate Node.js and browser implementations export them under explicit subpaths, for example @opentelemetry/sdk-logs/platform. If you depend on something that is only reachable through a deep import, please open an issue so it can be considered for the public API.
• feat(sdk-node)!: remove "jaeger" propagator from @opentelemetry/sdk-node #7077
  • OTEL_PROPAGATORS=jaeger and { jaeger: null } in the configuration object are no longer recognised. Replace with "tracecontext".
  • See the 3.x migration guide for full instructions.
• fix(opentelemetry-exporter-prometheus)!: default exporter host to localhost #6599 @​cjihrig
• chore!: bump minimum node.js version to >=22.15.0
• feat(api-logs)!: move the Logs API to @opentelemetry/api and remove the standalone @opentelemetry/api-logs package #4862 @​hectorhdzg
• fix(exporter-prometheus)!: stop reading Prometheus exporter host and port environment variables in the exporter constructor #6966 @​LarryHu0217
• chore(web-common)!: clean up and deprecate network span utils #7114
  • These utilities were long planned for removal. They were moved from the sdk-trace-web package and are currently only used by the (deprecated) instrumentation-fetch and instrumentation-xml-http-request packages.
  • Drop the skipOldSemconvContentLengthAttrs vestigial option from addSpanNetworkEvents().
• feat(sdk-node)!: drop SDK package re-exports (api, contextBase, core, logs, metrics, resources) #7111 @​pichlermarc
  • api / contextBase → import from @opentelemetry/api
  • core → import from @opentelemetry/core
  • logs → import from @opentelemetry/sdk-logs
  • metrics → import from @opentelemetry/sdk-metrics
  • resources → import from @opentelemetry/resources
• feat(sdk-logs): mark @opentelemetry/sdk-logs as stable #7143 @​trentm
  • See the stable CHANGELOG for future changes to the sdk-logs package.

... (truncated)

Commits

• 12a5817 chore: prepare next release (#7213)
• 2a97587 docs: 3.x migration doc edits (#7216)
• ebefa76 chore(deps): update dependency eslint to v10.13.0 (#7129)
• 83b6922 chore(deps): update dependency superagent to v10.4.1 (#7184)
• 68e9e6e fix(otlp-exporter-base): pick fetch mode from the document origin, not locati...
• 7d2455e build: lint for unused dependencies with knip (#7200)
• 5e65e0e fix(core): no longer drop an attribute value that is an object that has `un...
• 2fbb404 chore(deps): dedupe nx to 23.3.0 (#7205)
• c971f52 docs(changelog): trim unreleased entries (#7203)
• 2516215 feat(instrumentation)!: make InstrumentationBase#_enabled protected on both p...
• Additional commits viewable in compare view

[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.