Version conflict between Steeltoe.Management.OpenTelemetryBase and OpenTelemetry/OpenTelemetry.Extensions.Hosting in .NET 8 API project with Aspire

[vkvn]

I am encountering a version conflict when building a .NET 8 API project that references Steeltoe libraries, specifically Steeltoe.Management.OpenTelemetryBase. The build fails due to mismatched versions of OpenTelemetry and OpenTelemetry.Extensions.Hosting.

Detected package version outside of dependency constraint: Steeltoe.Management.OpenTelemetryBase 3.2.8 requires OpenTelemetry.Extensions.Hosting (>= 1.0.0-rc9.2 && <= 1.0.0-rc9.9) but version OpenTelemetry.Extensions.Hosting 1.9.0 was resolved.
Detected package version outside of dependency constraint: Steeltoe.Management.OpenTelemetryBase 3.2.8 requires OpenTelemetry (>= 1.2.0 && <= 1.3.2) but version OpenTelemetry 1.9.0 was resolved.

Environment:

.NET SDK: 8.0.0
Steeltoe Version: 3.2.8
OpenTelemetry.Extensions.Hosting Version: 1.9.0 (resolved version)
OpenTelemetry Version: 1.9.0 (resolved version)
Project Type: .NET 8 API (ASP.NET Core)
Aspire Platform: Used alongside Steeltoe

I would like to know if there are any plans to update the Steeltoe.Management.OpenTelemetryBase package to support the newer versions of OpenTelemetry (such as 1.9.0) and OpenTelemetry.Extensions.Hosting. The current version constraints in Steeltoe.Management.OpenTelemetryBase limit compatibility with these versions, which are now being widely used in projects targeting .NET 8.

[TimHess]

Hello @vkvn,

We are aware of this issue, and while I'd love to fix it in v3, but we believe there are too many breaking changes involved to fix it there (plus complexities around which .NET versions should be supported). We are nearing completion on a v4 release, which supports .NET 8+ and uses the latest OpenTelemetry and believe it's a better use of time to finish v4 than deal with the breakage and significant amount of testing that would be required to address this in v3