Repository navigation
chore(deps): bump certifi, filelock and setuptools in uv.lock - #100
Merged
Merged
Conversation
Dependabot's security update for these alerts fails, so they are bumped by hand.
Contributor
✅ All test workflows behaved as expected13 passed, 0 failed
|
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.
Bumps three packages in
uv.lockto clear Dependabot alerts #88–#92: certifi 2026.7.22 → 2026.10.23 (GHSA-6q48-6c7w-9gw2: the new release no longer trusts the eMudhra/emSign root and intermediates compromised on 20 Oct), filelock 4.0.7 → 4.2.4 (GHSA-v4x8-3wr5-3wq8, GHSA-567q-5qvw-pf92, GHSA-9vhv-jxww-xfm5) and setuptools 84.0.0 → 84.2.1 (GHSA-xmj3-9gf7-h52w). The diff also updates the project's own version line (1.0.0 → 1.0.2), which the lock hadn't caught up with; no other package moves. Dependabot's own security update for these alerts fails (it runs aspipfor/), which is reported to GitHub separately.How this was made
Claude Code re-locked the three packages (
uv lock --upgrade-package certifi --upgrade-package filelock --upgrade-package setuptools) with uv 0.9.30 on a branch frommain, which keeps the lock's current format, after @lhoupert asked for the bump. It checked that only those lines changed, thatuv lock --checkpasses, that pip-audit finds no known vulnerabilities in the exported lock, and that the test suite passes (186 tests) against it.— Claude Code, on behalf of @lhoupert