chore: prepare next release

[opentelemetrybot]

2.1.0

🚀 Features

• feat(opentelemetry-resources): add schema url #5070 @c-ehrlich

🐛 Bug Fixes

• fix(sdk-metrics): Remove invalid default value for startTime param to ExponentialHistogramAccumulation. This only impacted the closurescript compiler. #5763 @trentm

🏠 Internal

• chore: enable tsconfig isolatedModules #5697 @legendecas

0.204.0

💥 Breaking Changes

• feat(api-logs)!: Marked private methods as "conventionally private". #5789
• feat(exporter-otlp-*): support custom HTTP agents #5719 @raphael-theriault-swi
  • OtlpHttpConfiguration.agentOptions has been removed and functionality has been rolled into OtlpHttpConfiguration.agentFactory
    • (old) { agentOptions: myOptions }
    • (new) { agentFactory: httpAgentFactoryFromOptions(myOptions) }

🚀 Features

• feat(otlp-exporter-base): Add fetch transport for fetch-only environments like service workers. #5807
  • when using headers, the Browser exporter now prefers fetch over XMLHttpRequest if present. Sending via XMLHttpRequest will be removed in a future release.
• feat(opentelemetry-configuration): creation of basic ConfigProvider #5809 @maryliag
• feat(opentelemetry-configuration): creation of basic FileConfigProvider #5863 @maryliag
• feat(sdk-node): Add support for multiple metric readers via the new metricReaders option in NodeSDK configuration. Users can now register multiple metric readers (e.g., Console, Prometheus) directly through the NodeSDK constructor. The old metricReader (singular) option is now deprecated and will show a warning if used, but remains supported for backward compatibility. Comprehensive tests and documentation have been added. #5760

  • Migration:

    • Before:

      const sdk = new NodeSDK({ metricReader: myMetricReader });

    • After:

      const sdk = new NodeSDK({ metricReaders: [myMetricReader] });

  • Users should migrate to the new metricReaders array option for future compatibility. The old option will be removed in an upcoming experimental version.

• feat(instrumentation-http): Added support for redacting specific url query string values and url credentials in instrumentations #5743 @rads-1996

🐛 Bug Fixes

• fix(otlp-exporter-base): prioritize esnext export condition as it is more specific #5458
• fix(otlp-exporter-base): consider relative urls as valid in browser environments #5807
• fix(instrumentation-fetch): Use ESM version of semconv instead of CJS. Users expecting mixed ESM and CJS modules will now only get ESM modules. #5878 @overbalance

🏠 Internal

• refactor(otlp-exporter-base): use getStringFromEnv instead of process.env #5594 @weyert
• chore(sdk-logs): refactored imports #5801 @svetlanabrennan
• refactor(instrumentation-grpc): updated path to semconv #5884 @overbalance

[trentm]

Per #5901 (comment)

Release planned for tomorrow (Wed Sep 3, 2025)

[trentm]

• feat(instrumentation-http): Added support for redacting specific url query string values and url credentials in instrumentations #5743 ...

@pichlermarc This instr-http changelog entry under the 2.1.0 header seems misplaced. Sorry, I haven't looked into why.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 95.06%. Comparing base (4636de6) to head (d0d13c5).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #5903   +/-   ##
=======================================
  Coverage   95.06%   95.06%           
=======================================
  Files         307      307           
  Lines        8031     8031           
  Branches     1627     1627           
=======================================
  Hits         7635     7635           
  Misses        396      396           

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[raphael-theriault-swi]

@trentm Looks like it was just put into the wrong file by the author and no one caught it before merging

[pichlermarc]

Per #5901 (comment)

Release planned for tomorrow (Wed Sep 3, 2025)

I will postpone this until tomorrow since I did not get to it today.

[pichlermarc]

@trentm Looks like it was just put into the wrong file by the author and no one caught it before merging

Yep, I'll move it to the correct place before merging this.