Update @opentelemetry/api to latest version #10393
Conversation
|
@markwolff FYI |
|
Nice! I think the rush exception can be removed now too |
|
@markwolff There was a build error with |
|
Removed the rush exception in c56b4ad |
ramya-rao-a
requested review from
bterlson,
chradek,
daviwil,
HarshaNalluru,
jeremymeng,
jiacfan,
joheredi,
sophiajt,
KarishmaGhiya,
ljian3377,
mahdiva,
mikeharder,
richardpark-msft,
sadasant,
sarangan12,
schaabs,
vinjiang and
willmtemple
as code owners
| "@azure/logger": "^1.0.0", | ||
| "@opentelemetry/api": "^0.6.1", | ||
| "@opentelemetry/api": "^0.10.2", |
There was a problem hiding this comment.
Besides "change compile target to es5", is there any other changes involved and could influence end user?
There was a problem hiding this comment.
Looks this is the only change that affects us
There was a problem hiding this comment.
@jeremymeng: You want to look at all breaking changes between 0.6.1 and 0.10.2, not just the changes in the 0.10.2 release. I personally do not know if or how any of these breaking changes might impact our packages.
There was a problem hiding this comment.
Fortunately we use very little of their public surface area and active development has been in other areas
There was a problem hiding this comment.
oh that's right I was only looking at last release. But Jeff knows more!
There was a problem hiding this comment.
I went through all the release notes from 0.6.1 -- there were breaking changes in metrics (which we don't use yet), but not tracing.
This PR updates the version for
"@opentelemetry/api"to 0.10.2 to take in the fix open-telemetry/opentelemetry-js#1368 that fixes open-telemetry/opentelemetry-js#902which in turn fixes #9702