Repository navigation
chore(deps): Bump tango to v0.0.5 - #1005
Merged
Merged
Conversation
manjari25
requested review from
a team,
behinddwalls and
sbalabanov
as code owners
November 2, 2026 22:09
mnoah1
approved these changes
Nov 3, 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
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.
Why?
Bumps github.com/uber/tango from v0.0.46 to v0.0.51, the latest tagged release.
What?
The pin was five releases behind. Only the wire-level change is verified here: the request message dropped
roots_only, which nothing in this repo used. The rest oftango.protois unchanged, and the analyzer packages and the orchestrator server build and pass their tests.Test Plan
Issue