chore: bump direct Go dependencies#3801
Merged
Merged
Conversation
Assisted-By: docker-agent
…f0db to v1.0.0 Assisted-By: docker-agent
…o v0.0.0-20260722130236-0768e0998ac0 Assisted-By: docker-agent
Assisted-By: docker-agent
Assisted-By: docker-agent
docker-agent
left a comment
docker-agent
left a comment
Contributor
There was a problem hiding this comment.
Assessment: 🟢 APPROVE
aheritier
added
area/deps
trungutt
approved these changes
Jul 23, 2026
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
4 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.
Routine bump of direct Go dependencies. Each module was upgraded individually, with
task lintandtask testrun after every change to confirm the tree stayed green.The only test failures observed were pre-existing
TestLoadExamplesDMR cases that require Docker Model Runner at runtime; those fail on a clean checkout before any changes and are unrelated to this work.One candidate —
google.golang.org/adk— was skipped because the new release deprecatesadka2ain favour ofadka2a/v2and migrates to an iterator-basedExecutorAPI, which requires a non-trivial code migration. That will be handled separately.