How should evaluation evidence be versioned across ADK 1.x and 2.0? #6556
Unanswered
yuehua1213
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
ADK 2.0 introduces breaking changes to the agent API, event model, and session schema, while sessions have a specific compatibility boundary with 1.28+ and older 1.x versions. That makes versioned behavioral evidence especially important: a sample or agent may still load while producing different events, state transitions, or workflow behavior.
For teams evaluating reusable agents and workflows, it would help to bind each result to the ADK version, model, tools, session schema, task, observed output, failures, and environment.
Is there a recommended way to persist and compare evaluation evidence across the 1.x → 2.0 boundary, particularly for workflow routing and task delegation?
All reactions