traceloop / traceloop/openllmetry
π Bug Report: crewai instrumentation reports scope version 0.36.0 on 0.62.3 spans
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 7.4k
- Forks
- 1.1k
- Avg merge
- 8d 14h
- Merged PRs (30d)
- 2
Description
Which component is this bug for?
All Packages
π Description
Component: CrewAI Instrumentation β not in the dropdown, so "All Packages."
opentelemetry_instrumentation_crewai-0.62.3-py3-none-any.whl ships version.py containing __version__ = "0.36.0". That constant is passed to get_tracer and get_meter:
So every span and metric the package emits reports instrumentation scope version 0.36.0.
Scoped to this package β three siblings at the same release are correct:
| Package | dist | __version__ |
|---|---|---|
| anthropic | 0.62.3 | 0.62.3 |
| langchain | 0.62.3 | 0.62.3 |
| openai | 0.62.3 | 0.62.3 |
| crewai | 0.62.3 | 0.36.0 |
Likely cause. .cz.toml lists both crewai entries, but they behave differently:
"packages/opentelemetry-instrumentation-crewai/pyproject.toml:^version",
"packages/opentelemetry-instrumentation-crewai/opentelemetry/instrumentation/crewai/version.py",
The pyproject entry has a :^version regex anchor and bumps correctly (it's 0.62.3 in-tree). The bare version.py entry relies on commitizen finding the previous version string to replace β and since that file reads 0.36.0, there's nothing matching 0.62.2 to swap, so it's silently skipped every release.
That means correcting the file to 0.62.3 isn't a band-aid: it restores the string commitizen needs to match, after which the existing bump path keeps it in sync on its own.
π Reproduction steps
$ pip download opentelemetry-instrumentation-crewai==0.62.3 --no-deps
$ unzip -o opentelemetry_instrumentation_crewai-0.62.3-py3-none-any.whl -d x
$ cat x/opentelemetry/instrumentation/crewai/version.py
__version__ = "0.36.0"
$ grep ^Version: x/*.dist-info/METADATA
Version: 0.62.3
π Expected behavior
π Expected β version matches the released distribution, so instrumentation scope reflects the installed package.
π Actual β spans and metrics report scope 0.36.0 on a 0.62.3 install; anyone version-gating or debugging off
π Actual Behavior with Screenshots
N/A
π€ Python Version
N/A (packaging metadata)
π Provide any additional context for the Bug.
No response
π Have you spent some time to check if this bug has been raised before?
- I checked and didn't find similar issue
Are you willing to submit PR?
Yes I am willing to submit a PR!
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up β it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with packages/opentelemetry-instrumentation-crewai/opentelemetry/instrumentation/crewai/version.py and compare it with the package's pyproject.toml and the instrumentation.py references at lines 77 and 80. Reproduce with the 0.62.3 wheel commands in the issue, then verify that version.py reports the released distribution version and instrumentation scope no longer reports 0.36.0.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- observability
- Issue type
- Bug
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Active
- Clarity
- Clearly specified
- Newbie friendliness
- 92/100