Conversation
zanieb
approved these changes
Nov 12, 2025
fc78b02 to
b065405
Compare
b065405 to
484c900
Compare
484c900 to
d4c751b
Compare
charliermarsh
approved these changes
Nov 12, 2025
d4c751b to
d35c92a
Compare
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.
Summary
This PR makes uv attach linehaul data to the user agent in cases when marker values for a Python interpreter weren't passed in to the registry clients (e.g.
uv auth login)Test Plan
Observe the right user agent string being attached for
uv auth login. Not sure this warrants a test case, but happy to add one.