Uh oh!
There was an error while loading. Please reload this page.
Stop internal PyPI proxy URLs from leaking into uv.lock - #5800
Merged
Conversation
When uv/pip points at the internal *.databricks.com PyPI proxy, pydabs-codegen's `uv run` rewrites `source.registry` in the lockfiles to the proxy instead of pypi.org. This churn has leaked into several SDK-bump PRs, each needing a manual revert. pydabs-codegen now reverts the lockfiles after regenerating, and a new `check-uv-lock` (in `task checks`) backstops against a proxy URL reaching a committed lock any other way. The redundant checkout in push.yml is removed. Co-authored-by: Isaac
simonfaltum
approved these changes
Jul 2, 2026
pietern
enabled auto-merge
July 2, 2026 12:37
Collaborator
Integration test reportCommit: b68b3a0
23 interesting tests: 13 SKIP, 10 RECOVERED
Top 6 slowest tests (at least 2 minutes):
|
Uh oh!
There was an error while loading. Please reload this page.
yansonggao-db pushed a commit
to yansonggao-db/cli
that referenced
this pull request
Jul 21, 2026
…ks#5994) `generate-clijson` re-syncs the genkit tagging locks; in a proxy-configured environment uv bakes the internal PyPI proxy URL into them. databricks#5800 added the guard + pydabs revert for `*uv.lock`, but the genkit `*.py.lock` files fell through and re-leaked into databricks#5982 (hand-scrubbed there). This closes the gap by scrubbing the proxy URL in generate-clijson and widening check-uv-lock's glob to cover the genkit locks. This pull request and its description were written by Isaac.
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 freeto 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.
When uv/pip points at the internal *.databricks.com PyPI proxy, pydabs-codegen's
uv runrewritessource.registryin the lockfiles to the proxy instead of pypi.org. This churn has leaked into several SDK-bump PRs, each needing a manual revert.pydabs-codegen now reverts the lockfiles after regenerating, and a new
check-uv-lock(intask checks) backstops against a proxy URL reaching a committed lock any other way. The redundant checkout in push.yml is removed.This pull request and its description were written by Isaac.