Exporter - An improper ref in v1.15.0

[Gabizar]

opentelemetry-python/exporter/opentelemetry-exporter-otlp-proto-grpc/src/opentelemetry/exporter/otlp/proto/grpc/exporter.py

Line 56 in 19ce125

from opentelemetry.util.re import parse_env_headers

^ in here parse_env_headers is being imported.
but this version (1.15.0) in its pyproject.toml points to opentelemetry-api version 1.12.0 which does not contain parse_env_headers but parse_headers instead

v1.14.0 imported parse_headers correctly

[srikanthccv]

Thanks for the report. This has come up once previously and discussed here #2444. This is going to be a priority to catch this earlier.

[marianogappa]

According to this https://github.com/open-telemetry/opentelemetry-python/releases at the moment I wrote this, 1.15.0 continues to be the latest release.

This means that the current minor version is a release that causes a raise. Is the maintainer planning to issue a patch release fixing the bug? Otherwise, anyone who is importing this package and updates their deps is gonna succeed to release, but then have an outage in production.

We just recovered from an outage due to this. Our workaround was to prevent dependency resolution to pick 1.15.0 specifically.

[MrwanBaghdad]

We're also facing this. We were lucky to catch it before rolling it out to prod. Please prioritise

[Symbianx]

@srikanthccv I see this marked as fixed from the PR. When can we expect this to be released?

[adambregenzer]

@srikanthccv et. al. is there an update on when a new release will go out, or perhaps a hotfix to address this problem specifically? Unless I'm missing something 1.15 is unusable as-is. We have pinned ourselves to 1.14 while waiting for this. It's not a dealbreaker to be on 1.14 but it's concerning that this package has been broken for so long.

[srikanthccv]

Ideally, the release which included the fix should have been out already. There were some logistical issues which delayed the release. It should be out soon.