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
This only affects the JavaScript OpenTelemetry library
This may affect other libraries, but I would like to get opinions here first
In #2737 API range was extended from >=1.0.0 <1.1.0 to >=1.0.0 <1.2.0 to add support for 1.1 but keep compatible as much as possible.
Unfortunately this resulted in broken CI for nodejs 16 (see #2755).
In #2759 API version range in SDKs was narrowed to >=1.1.0 <1.2.0 to fix the CI.
I think we should clarify how to continue here and if more changes then hat one done in #2759 are needed to stay consistent or if we should revert it and solve the CI problem in a different way.
In general allowing SDK to use an 1.0 API seems to be problematic as it avoids that e.g. instrumentation use API 1.1. Reason is that SDK registers TracerProvider,.. in version 1.0 and the version check in API doesn't accept newer minor (only olders).
The text was updated successfully, but these errors were encountered:
In #2737 API range was extended from
>=1.0.0 <1.1.0
to>=1.0.0 <1.2.0
to add support for 1.1 but keep compatible as much as possible.Unfortunately this resulted in broken CI for nodejs 16 (see #2755).
In #2759 API version range in SDKs was narrowed to
>=1.1.0 <1.2.0
to fix the CI.I think we should clarify how to continue here and if more changes then hat one done in #2759 are needed to stay consistent or if we should revert it and solve the CI problem in a different way.
In general allowing SDK to use an 1.0 API seems to be problematic as it avoids that e.g. instrumentation use API 1.1. Reason is that SDK registers TracerProvider,.. in version 1.0 and the version check in API doesn't accept newer minor (only olders).
The text was updated successfully, but these errors were encountered: