You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As preparation for OTEL v2 we need to do the following:
Make sure we don't re-export any OTEL TS declarations in any way shape or form because they will bump to 5.6ish which is way above our desired pain threshold for our users. The only way we can stay compatible is if our .d.ts files don't reference any @opentelemetry/* packages at all. If we do so, we need to deprecate them immediately.
The text was updated successfully, but these errors were encountered:
Aligning with DT's policy actually seems quite reasonable to me and it would be a reasonable amount of maintenance going forward. I am only worried about what this means process-wise when DT and/or OTEL bump their minimum version. Do we always need to inform users? Will things break? Potentially, this would allow us to stop downleveling our types because we have a policy to follow.
Superficially trying this it seems rather tedious and error-prone. If possible I'd like to avoid this.
There are a lot of question marks tied to the exact details of this approach. Does it work reliably? Does it work at all? We would also need to start forking downlevel-dts.
Description
As preparation for OTEL v2 we need to do the following:
@opentelemetry/*
packages at all. If we do so, we need to deprecate them immediately.The text was updated successfully, but these errors were encountered: