fix(ci): clear pip-audit --strict vulns blocking redis 8.1.0 bump (click, cryptography) - #193
Draft
Sbussiso wants to merge 1 commit into
Draft
fix(ci): clear pip-audit --strict vulns blocking redis 8.1.0 bump (click, cryptography)#193Sbussiso wants to merge 1 commit into
Sbussiso wants to merge 1 commit into
Conversation
CI run #575 (32071459890) failed the pip-audit --strict step on the dependabot/uv/backend/redis-8.1.0 branch. The redis bump itself is fine; the scan found 4 advisories in 2 transitive packages that landed in the PyPA advisory DB after the last green deploy: click 8.3.1 PYSEC-2026-2132 (fix: 8.3.3) cryptography 48.0.1 PYSEC-2026-3552 (fix: 50.0.0) cryptography 48.0.1 PYSEC-2026-3553 (fix: 49.0.0) cryptography 48.0.1 PYSEC-2026-3554 (fix: 49.0.0) Fix follows the repo's established pattern (constraint-dependencies in [tool.uv] for transitive CVE pins): - cryptography>=48.0.1 -> >=50.0.0 (clears all 3 advisories) - click>=8.3.3 (new constraint, clears PYSEC-2026-2132) Note: bumping cryptography to 50.0.0 forces clerk-backend-api 6.0.1 -> 7.0.0 because clerk 6.x requires cryptography<49.0.0. clerk 7.0.0 is the first release supporting cryptography 50.x. The app uses only Clerk(), clerk.authenticate_request, AuthenticateRequestOptions, and clerk.organizations.update — all present in 7.0.0. Full test suite (699 tests) passes; pip-audit --strict is clean. Verified locally: - uv lock --check: consistent - uv run pip-audit --strict: No known vulnerabilities found - uv run pytest tests/: 699 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
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
CI run #575 (32071459890) failed the pip-audit --strict step on this Dependabot branch (
dependabot/uv/backend/redis-8.1.0).The redis 7.4.0 → 8.1.0 bump is fine — the failure is caused by 4 advisories in 2 transitive packages that landed in the PyPA advisory DB after the last green deploy, unrelated to redis:
Fix
Follows the repo's established pattern —
constraint-dependenciesin[tool.uv]for transitive CVE pins:cryptography>=48.0.1→>=50.0.0(clears all 3 cryptography advisories)click>=8.3.3(new constraint, clears PYSEC-2026-2132)Bumping cryptography to 50.0.0 forces clerk-backend-api to 7.0.0 because clerk 6.x requires
cryptography<49.0.0. clerk 7.0.0 is the first release supporting cryptography 50.x — this is not optional.The app's clerk SDK surface is thin and all APIs used are present in 7.0.0:
Clerk(bearer_auth=...)— instantiationclerk.authenticate_request(...)— request authAuthenticateRequestOptions— auth optionsclerk.organizations.update(...)— org member limitVerification (all run locally in the sandbox)
uv lock --checkuv run pip-audit --strictuv run pytest tests/Triage
Opened by Hermes coder CI triage for run 32071459890.