chore: release proposal 0.18.0

[dyladan]

https://github.com/open-telemetry/opentelemetry-js/releases/tag/untagged-054b13e1f863d8ea300c

🐛 (Bug Fix)

• opentelemetry-exporter-collector-grpc, opentelemetry-exporter-collector
  • #1938 fix(exporter-collector): wrong data type for numbers (@kudlatyamroth)
• opentelemetry-instrumentation-http, opentelemetry-plugin-http
  • #1939 fix: use socket from the request (@mzahor)
• opentelemetry-context-async-hooks
  • #1937 fix: isolate binding EventEmitter (@Flarna)

📚 (Refine Doc)

• #1973 docs(readme): fix @opentelemetry/instrumentation-http link (@Hongbo-Miao)
• #1941 fix: update readme upgrade guidelines version setting (@MSNev)

🏠 (Internal)

• opentelemetry-api-metrics, opentelemetry-context-async-hooks, opentelemetry-context-zone-peer-dep, opentelemetry-core, opentelemetry-exporter-collector-grpc, opentelemetry-exporter-collector-proto, opentelemetry-exporter-collector, opentelemetry-exporter-jaeger, opentelemetry-exporter-prometheus, opentelemetry-exporter-zipkin, opentelemetry-grpc-utils, opentelemetry-instrumentation-fetch, opentelemetry-instrumentation-grpc, opentelemetry-instrumentation-http, opentelemetry-instrumentation-xml-http-request, opentelemetry-instrumentation, opentelemetry-metrics, opentelemetry-node, opentelemetry-plugin-grpc-js, opentelemetry-plugin-grpc, opentelemetry-plugin-http, opentelemetry-plugin-https, opentelemetry-propagator-b3, opentelemetry-resource-detector-aws, opentelemetry-resource-detector-gcp, opentelemetry-resources, opentelemetry-sdk-node, opentelemetry-shim-opentracing, opentelemetry-tracing, opentelemetry-web
  • #1977 chore: update API to 0.18.0 (@Flarna)
• Other
  • #1960 chore: updating current state of compatibility matrix (@obecny)
• opentelemetry-api-metrics, opentelemetry-api, opentelemetry-context-async-hooks, opentelemetry-context-base, opentelemetry-context-zone-peer-dep, opentelemetry-core, opentelemetry-exporter-collector-grpc, opentelemetry-exporter-collector-proto, opentelemetry-exporter-collector, opentelemetry-exporter-jaeger, opentelemetry-exporter-prometheus, opentelemetry-exporter-zipkin, opentelemetry-grpc-utils, opentelemetry-instrumentation-fetch, opentelemetry-instrumentation-grpc, opentelemetry-instrumentation-http, opentelemetry-instrumentation-xml-http-request, opentelemetry-instrumentation, opentelemetry-metrics, opentelemetry-node, opentelemetry-plugin-grpc-js, opentelemetry-plugin-grpc, opentelemetry-plugin-http, opentelemetry-plugin-https, opentelemetry-propagator-b3, opentelemetry-resource-detector-aws, opentelemetry-resource-detector-gcp, opentelemetry-resources, opentelemetry-sdk-node, opentelemetry-shim-opentracing, opentelemetry-tracing, opentelemetry-web
  • #1942 chore: remove API and context-base (@dyladan)
• opentelemetry-core, opentelemetry-exporter-collector, opentelemetry-instrumentation-http, opentelemetry-metrics, opentelemetry-plugin-http
  • #1922 chore: lint on shadowing in non-test sources, fix a few of them (@johnbley)

Committers: 8

• Bartlomiej Obecny (@obecny)
• Daniel Dyla (@dyladan)
• Gerhard Stöbich (@Flarna)
• Hongbo Miao (@Hongbo-Miao)
• John Bley (@johnbley)
• Karol Fuksiewicz (@kudlatyamroth)
• Marian Zagoruiko (@mzahor)
• Nev (@MSNev)

[codecov]

Codecov Report

Merging #1982 (e37bc33) into main (41235a9) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main    #1982   +/-   ##
=======================================
  Coverage   92.92%   92.92%           
=======================================
  Files         152      152           
  Lines        5922     5922           
  Branches     1245     1245           
=======================================
  Hits         5503     5503           
  Misses        419      419           

[vmarchaud]

not related but does the 0.18 should be the RC for the API ?

[dyladan]

Is it sufficient to put on the README for the API that 0.18 is the release candidate? Or do we want to release something like 1.0.0-rc.1?

Opened an issue in API open-telemetry/opentelemetry-js-api#15. This isn't really the right place to discuss it.

[obecny]

lgtm,
in section :house (Internal) is this extra information added automatically or accidently ?

`opentelemetry-api-metrics`, `opentelemetry-context-async-hooks`, `op ....

[dyladan]

lgtm,
in section :house (Internal) is this extra information added automatically or accidently ?

`opentelemetry-api-metrics`, `opentelemetry-context-async-hooks`, `op ....

I intentionally added it to the lerna.json so that it would be added automatically from now on.