chore: 0.15.0 release proposal

[github-actions]

This is an auto-generated release PR. If additional changes need to be incorporated before the release, the CHANGELOG must be updated manually.

Merging this PR will automatically release all packages to NPM.

[obecny]

missing otel dependencies being updated to latest in propagators, examples, metapackages (auto), detectors
it wasn't updated here -> #408

[Flarna]

Some PRs are missing in the changelog: #386, #338, #394, #351

[dyladan]

Those PRs were missing labels. I'll update the changelog.

[dyladan]

missing otel dependencies being updated to latest in propagators, examples, metapackages (auto), detectors
it wasn't updated here -> #408

It was just a patch update so the examples shouldn't be affected. Only reason it needed to be done in #408 was to ensure dependency resolution didn't get messed up

Also, the dependencies use the ^ range which means they should get the latest patch versions anyway.

[codecov]

Codecov Report

Merging #409 (e7eb898) into main (55fa0e9) will decrease coverage by 0.21%.
The diff coverage is 33.33%.

❗ Current head e7eb898 differs from pull request most recent head ee7cdf9. Consider uploading reports for the commit ee7cdf9 to get more accurate results

@@            Coverage Diff             @@
##             main     #409      +/-   ##
==========================================
- Coverage   94.43%   94.21%   -0.22%     
==========================================
  Files          11       12       +1     
  Lines         431      432       +1     
  Branches       48       48              
==========================================
  Hits          407      407              
- Misses         24       25       +1     

Impacted Files	Coverage Δ
...apackages/auto-instrumentations-web/src/version.ts	0.00% <0.00%> (ø)
...s/opentelemetry-propagator-ot-trace/src/version.ts	0.00% <0.00%> (ø)
packages/opentelemetry-host-metrics/src/version.ts	100.00% <100.00%> (ø)

[dyladan]

Changelog fixed. @obecny I don't think the examples need to be updated since they are ^ range dependencies so they should get the latest anyway. In any case the release PR should probably be kept only to things pertaining to release. Other version changes can be done in another PR if needed.

[obecny]

Changelog fixed. @obecny I don't think the examples need to be updated since they are ^ range dependencies so they should get the latest anyway. In any case the release PR should probably be kept only to things pertaining to release. Other version changes can be done in another PR if needed.

Can we endup with having mixed version of api 0.18, 0.18.1 and rc, and because people will be able to use version 0.18.0, 0.18.1 and 0.18.2 of core plugins where 0.18.1 is broken ?

[dyladan]

Changelog fixed. @obecny I don't think the examples need to be updated since they are ^ range dependencies so they should get the latest anyway. In any case the release PR should probably be kept only to things pertaining to release. Other version changes can be done in another PR if needed.

Can we endup with having mixed version of api 0.18, 0.18.1 and rc, and because people will be able to use version 0.18.0, 0.18.1 and 0.18.2 of core plugins where 0.18.1 is broken ?

Everything that uses the ^ version range will receive the latest matching version which is 0.18.2. If they installed a pinned 0.18.1 somewhere it would be broken, but they should not have some dependencies pinned and others not.