Skip to content

fix: derive integration attribution from package version#2

Merged
OndrejDrapalik merged 1 commit into
mainfrom
fix/integration-attribution-version
Jul 16, 2026
Merged

fix: derive integration attribution from package version#2
OndrejDrapalik merged 1 commit into
mainfrom
fix/integration-attribution-version

Conversation

@OndrejDrapalik

Copy link
Copy Markdown
Contributor

Summary

Keep E2B integration attribution tied to installed e2b-adk package version instead of duplicating 0.1.0 in runtime code and tests.

Without this, a future package version bump could keep reporting traffic as e2b-adk/0.1.0, corrupting integration adoption and version telemetry while tests still pass.

Changes

– Export __version__ from installed package metadata.
– Build ConnectionConfig integration token from __version__.
– Verify attribution against same package metadata in tests.

Verification

uv run pytest tests/test_plugin.py -q — 14 passed.
uv run ruff check e2b_adk tests examples — passed.
uv run mypy e2b_adk — passed.
– Built wheel and sdist; twine check dist/* passed.

Context

Follow-up from release-path research: https://linear.app/e2b/issue/INT-47/google-adk-code-generator

@cla-bot cla-bot Bot added the cla-signed label Jul 16, 2026
@OndrejDrapalik
OndrejDrapalik merged commit 3d4a0b2 into main Jul 16, 2026
9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant