chore: prepare next release

[otelbot-js]

0.206.0

🚀 Features

• feat(otlp-transformer): add span flags support for isRemote property #5910 @nikhilmantri0902
• feat(sampler-composite): Added experimental implementations of draft composite sampling spec #5839 @anuraaga
• feat(opentelemetry-configuration): add more attributes to config model #5826 @maryliag
• feat(opentelemetry-configuration): Parse of Configuration File #5875 @maryliag
• feat(opentelemetry-configuration): parse of array objects on configuration file #5947 @maryliag
• feat(opentelemetry-configuration): parse of environment variables on configuration file #5947 @maryliag

🐛 Bug Fixes

• fix(instrumentation-http): respect requireParent flag when INVALID_SPAN_CONTEXT is used #4788 @reberhardt7
• fix(otlp-transformer): trunc hrTime to int for nanos converting #5924 @blumamir

🏠 Internal

• refactor(otlp-exporter-base): use get*FromEnv() for otlp exporter config. #5583 @weyert

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 95.17%. Comparing base (06621d2) to head (bbf54e1).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #5976   +/-   ##
=======================================
  Coverage   95.17%   95.17%           
=======================================
  Files         316      316           
  Lines        8521     8521           
  Branches     1763     1763           
=======================================
  Hits         8110     8110           
  Misses        411      411           

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

[pichlermarc]

The failing tests are likely my fault, as I changed the release PR creation script in #5965. I'll look into it.

[pichlermarc]

Looks like I might've messed up the lock file in my PR. Let's try again after #5977 is merged.

[pichlermarc]

hmm, it looks like npm@<11 does not like the lockfile produced by this PR. 🤔

[pichlermarc]

Similar problems seem to occur for renovate bot #5975

[pichlermarc]

I suppose there's a difference in resolution between npm@11 and npm@10 when using lockfile-version=2.

I tested locally with lockfile-version=3 and then the release PR script works. We'd likely also be able to use an older npm version for creating the release PR, but upgrading to a later lockfile seems better to me than keeping to use outdated deps.

I'll open a PR tomorrow to update it.

[pichlermarc]

I think I narrowed it down to npm@11.6.1 doing things differently now. I'll open a PR to pin to npm@11.6.0 and will try again.

[pichlermarc]

package-lock.json looks better now. Let's see if the tests pass and then we can release on Monday. 🙂