[BUG CLIENT]: opentelemetry-api is pinned to 1.39.x

[BjoernPetersen]

Python -VV

Python 3.14.6 (main, Jun 23 2026, 18:14:05) [GCC 16.1.1 20260430]

Pip Freeze

annotated-types==0.7.0
anyio==4.14.2
certifi==2026.6.17
eval_type_backport==0.4.0
h11==0.16.0
httpcore==1.0.9
httpx==0.28.1
idna==3.18
importlib_metadata==8.7.1
jsonpath-python==1.1.6
mistralai==2.5.2
opentelemetry-api==1.39.1
opentelemetry-semantic-conventions==0.60b1
pydantic==2.13.4
pydantic_core==2.46.4
python-dateutil==2.9.0.post0
six==1.17.0
typing-inspection==0.4.2
typing_extensions==4.16.0
zipp==4.1.0

Reproduction Steps

1. Try either pip install 'mistralai==2.5.2' 'opentelemetry-api<1.39' or pip install 'mistralai==2.5.2' 'opentelemetry-api>=1.40'
2. Observe pip failing to resolve the dependencies

Expected Behavior

Your pyproject.toml indicates to me that you intended to support opentelemetry-api versions 1.31.1 and upward, as long as they're backwards-compatible according to semver:

opentelemetry-api (>=1.33.1,<2.0.0)

However, every release of the opentelemetry packages depends on a specific version of the supporting packages (instrumentation, semantic conventions, etc.), and you pinned the opentelemetry-semantic-conventions package as well:

"opentelemetry-semantic-conventions (>=0.60b1,<0.61)"

This means your mistralai package restricts users to a specific version of the opentelemetry packages.

Additional Context

No response

Suggested Solutions

Either widen the version constrains for opentelemetry-semantic-conventions or entirely omit the version constraint for that dependency. I'd recommend the latter, because the package version will be dictated/pinned by the opentelemetry-api package as well, and specifying versions for both packages will just make dependency updates harder to coordinate.

In pyproject.toml:

dependencies = [
    # [...]
    "opentelemetry-api (>=1.33.1,<2.0.0)",
    "opentelemetry-semantic-conventions",
]