chore: prepare release 1.20.0/0.47.0

[pichlermarc]

1.20.0

🚀 (Enhancement)

• perf(otlp-transformer): skip unnecessary base64 encode of span contexts #4343 @seemk
• feat(sdk-trace-base): improve log messages when dropping span events #4223 @mkubliniak

0.47.0

🐛 (Bug Fix)

• fix(instrumentation): use caret range on import-in-the-middle #4380 @pichlermarc

[codecov]

Codecov Report

Merging #4382 (1f4873f) into main (f4b681d) will not change coverage.
The diff coverage is n/a.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #4382   +/-   ##
=======================================
  Coverage   92.22%   92.22%           
=======================================
  Files         333      333           
  Lines        9459     9459           
  Branches     2009     2009           
=======================================
  Hits         8724     8724           
  Misses        735      735           

[dyladan]

@pichlermarc does the IITM fix help the contrib issue? Something you mentioned earlier today made me think you were second-guessing that.

[pichlermarc]

@pichlermarc does the IITM fix help the contrib issue? Something you mentioned earlier today made me think you were second-guessing that.

Yep, I think it may be better to hold off on this release until after the holidays. I think the problems we're having in contrib won't be fixed by updating to 1.7.2.

There the problem is that we use export * to re-export from @opentelemetry/instrumentation-http. This would work in 1.7.2 if it was an ESM module, but since @opentelemetry/instrumentation-http is actually loaded as CJS the re-exports are not working when the import-in-the-middle hook is registered on Node 18.19 and Node 20.

This is only the first problem we encounter it fails at. We have many re-exports using export * and other packages could have that too, so the ESM tests in contrib will likely continue to fail until there's solution in iitm for that.

[trentm]

This is only the first problem we encounter it fails at. We have many re-exports using export * and other packages could have that too, so the ESM tests in contrib will likely continue to fail until there's solution in iitm for that.

I've opened open-telemetry/opentelemetry-js-contrib#1873 to temporarily pin to Node.js v18.18.2 until we can get an IITM fix in.