Repository navigation
Promote staging to production (da36f4e) - #680
Merged
Merged
Conversation
Stainless-Generated-From: bc2fde55f57ad8d984a7d619c0bde5022a4b66d2
Repairs the fork from the squash-merged promote. Production's commits since the fork are a squashed copy of the staging feat commit plus the 0.35.0 release, so this keeps staging's code and takes production's release-please files.
ci: merge production main into the staging trunk
…-adk 2.x Each Runner.run_async call is now one trace rooted at an "Agent turn: <app>" step, on google-adk 1.x and 2.x alike. ADK 2.x runs every agent in its own asyncio task, which split a multi-agent turn into one trace per agent. Turns - The turn's context is swapped in only while ADK's generator runs, so a caller that breaks out on the final response, returns mid-turn from a @trace handler, or resumes from a new task per event still gets one trace per turn and keeps a clean context. - Failed or cancelled turns and agents record the error and get no "Agent execution completed" placeholder. Handoffs - Recorded from the event the transferring agent authors with actions.transfer_to_agent set, as a "Handoff: A → B" HandoffStep. Custom tools and callbacks that set the action count; failed or duplicate transfer_to_agent calls don't. - The receiving agent nests under the transferring agent's parent, so transfers inside workflow agents and AgentTools stay in place. An AgentTool's nested Runner keeps its own handoff scope. - starting_agent, final_agent, handoff_count and handoff_path are written as trace metadata (row columns), combined when one @trace runs several turns. - Drop the "description contains 'transfer'" heuristic, which hid real tools such as executar_transferencia_pix. google-adk 2.9 / 2.10 (OPEN-12518) - Patch the tool-call function where each version defines it: functions (<= 2.8), _tool_caller (2.9) and tools._caller (>= 2.10), falling back to the module functions.py's re-export names. Steps, outputs and columns - Tool steps and tool callbacks are siblings of LLM calls under the agent step; the platform doesn't store usage for an LLM step with children. - Gemini models use the "gemini" provider slug and a bare model name. Thinking tokens count as completion tokens unless the totals show they're already in candidates (LiteLlm, ApigeeLlm). - The turn step carries the first agent's attributes as inputs; every agent's user_query is the Runner's message. Workflow agents keep their children's answer; thought parts are left out of outputs; a tool-result-only final response uses that result. - Empty Gemini replies (parts=None) no longer crash the turn; raw_output leaves out inline_data bytes; before_model sorts just before its LLM call. - Close wrapped ADK generators explicitly, which stops OpenTelemetry's "Failed to detach context" errors. CI runs the integrations job on the latest google-adk plus a google-adk<2 step for the ADK tests. The chaining test now compares against an untraced run, since ADK 2.x chains its own DynamicNodeFailError. Refs OPEN-12518 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01XLytNqP82mzPV9qRvrMaiv
…ndoffs feat(OPEN-12864): record Google ADK agent handoffs and support google-adk 2.x
viniciusdsmello
approved these changes
Oct 6, 2026
viniciusdsmello
left a comment
viniciusdsmello
left a comment
Contributor
There was a problem hiding this comment.
Promote OPEN-12864 (Google ADK handoffs + google-adk 2.x support). CI green.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Promotes
openlayer-ai/openlayer-pythonmainto the staging trunk (da36f4e).Merge with a merge commit — do not squash or rebase. Squashing rewrites the commits and forks the trunks; the next back-sync and promote refuse until repaired by hand.
After merging, release-please opens the version PR on this repo; merging that one tags and publishes.
Commits