Skip to content

fix: support Google ADK 2.12-2.14 - #1224

Open
evanlowe wants to merge 1 commit into
volcengine:mainfrom
evanlowe:fix/adk-2.14-compat
Open

evanlowe wants to merge 1 commit into
volcengine:mainfrom
evanlowe:fix/adk-2.14-compat

Conversation

@evanlowe

Copy link
Copy Markdown
Contributor

Summary

Allow Google ADK 2.12–2.14 while preserving VeADK tracing and Studio startup. Upgrading without these changes can fail on the native telemetry hook's new signature or lose model spans, session trace lookup, and token totals as ADK changes its tracing context and default schema.

  • Widen both base and eval dependencies to google-adk>=2.7.0,<2.15.0 and update the lock file. Python 3.10 continues to resolve ADK 2.11; newer Python versions can use ADK 2.14.1.
  • Adapt invocation and agent trace contexts across ADK generations, forward telemetry configuration arguments, and retain VeADK call_llm spans under the new default schema. Preserve context cleanup on cancellation, early stream closure, and model errors without requiring a legacy telemetry environment setting.
  • Keep Studio startup lazy with newer GenAI enums, evaluation imports/session prefixes, and artifact utilities. Derive enum values and the current evaluation prefix from the installed SDK.

Validation

Validated locally on 2026-11-18 after fetching and rebasing onto the current origin/main (622e7a21).

Check Result
uv run --no-sync --extra dev pre-commit run --all-files pass: Ruff checks/format, Gitleaks, dependency policy, YAML secret scan
uv run --no-sync --extra dev pytest -n 2 -m "not codex_smoke and not piagent_smoke" pass: 9,334 passed, 137 skipped, 4 expected failures; no failures (2 workers)
ADK compatibility/tracing regressions pass on 2.7.0, 2.7.1, 2.11.0, 2.12.0, 2.13.0, and 2.14.1, using extracted ADK wheels with the project environment
Startup and tracing regressions on Python 3.10 / ADK 2.11 pass: 49 tests in a separately resolved Python 3.10 environment
Built wheel in a clean Python 3.12 environment pass: 19 startup/tracing tests with ADK 2.14.1; installed dependency consistency check and eval extra resolution
scripts/check_dependency_e2e.py declared-range against the built wheel pass: highest allowed versions of the checked runtime dependencies resolve
Pyright on changed Python files fail: 37 existing diagnostics; no new diagnostics compared with the base sources under the same dependencies (43 diagnostics)

The project test environment includes the dev, extensions, sandbox, and codex extras; --no-sync preserves those installed test dependencies. Runtime tests use local fake models and in-memory exporters. Real provider/cloud calls and opt-in Codex/Pi smoke runs were not run. Frontend UI/build checks are not applicable because no frontend source changed.

Compatibility and limits

Existing public entry points and configuration remain supported. ADK 2.15+ stays excluded because this adapter depends on upstream telemetry internals. The Pyright baseline issues are outside this compatibility fix.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant