Comment From: wilkinsona
This upgrade requires some further investigation as it causes 3 failures in BaggagePropagationIntegrationTests.
Comment From: chicobento
Hi @wilkinsona , we stumble upon issue https://github.com/open-telemetry/opentelemetry-java/issues/4918 regarding the usage of EC certificates with open-telemetry 1.19. The issue was fixed on otel 1.20.0. Is there any chance of bumping otel to 1.20 for upcoming 3.0.3 ? Perhaps failures on BaggagePropagationIntegrationTests will not happen on 1.20.0.
ps: I know we can always override the bom version on the application level, but just saying.
Comment From: wilkinsona
Is there any chance of bumping otel to 1.20 for upcoming 3.0.3 ?
Unfortunately not. Whenever possible, we aim to only upgrade to new maintenance releases of dependencies in Boot's maintenance releases. If we'd shipped 3.0.0 with 1.20, we could have upgraded to 1.20.1 in a 3.0.x release, but we won't jump from 1.19.0 to 1.20 or later in 3.0.x.
I know we can always override the bom version on the application level, but just saying.
If you want to opt in to a new minor release, this is what you should do.
Comment From: chicobento
Just a curious thing, looking at otel-sdk release history they have rarely released patch versions so it looks like a Boot minor will be constantly behind and never get bug fixes. Hope that as otel-sdk get more stable they start following a more stable release cycle.
That said, the policy to keep 3pp minors within a Boot minor makes completely sense as it is complex to handle all the 3pps and their commitment to semver and minors maintenance. 👍🏻
Comment From: eduanb
Also worth noting is that 1.20 is needed to get Graal Native to work. Otherwise, you will see this error:
Caused by: java.lang.NoSuchFieldException: producerIndex
Here is the PR with more info https://github.com/open-telemetry/opentelemetry-java/pull/4832