Fix click and setuptools advisories in exp lockfiles#363
Merged
Conversation
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
1 participant
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
Fixes the two advisories that turned the post-merge OSV Scanner red on dev starting 2026-07-14 (published upstream against unchanged code; the same commit passed on 2026-07-13):
exp/zlup/uv.lock(fix landed in 8.3.3)exp/zluppy/uv.lockRoot
uv.lockalready carries setuptools 83.0.0; only the experimental lockfiles were stale. Locks regenerated with uv 0.11.14 (the CI pin); the diff is 2 hunks, version/checksum lines for the two packages only.This unblocks the py-0.9.0.dev1 release path, which requires all post-merge workflows green.
Validation
git diffcontains no changes outside the click and setuptools entries