fix(backend): clear pip-audit --strict on new cryptography/click advisories (CI #570) - #191
Draft
Sbussiso wants to merge 4 commits into
Draft
Conversation
Bumps [ruff](https://github.com/astral-sh/ruff) from 0.16.2 to 0.16.3. - [Release notes](https://github.com/astral-sh/ruff/releases) - [Changelog](https://github.com/astral-sh/ruff/blob/main/CHANGELOG.md) - [Commits](astral-sh/ruff@0.16.2...0.16.3) --- updated-dependencies: - dependency-name: ruff dependency-version: 0.16.3 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps [hls.js](https://github.com/video-dev/hls.js) from 1.6.16 to 1.7.0. - [Release notes](https://github.com/video-dev/hls.js/releases) - [Changelog](https://github.com/video-dev/hls.js/blob/master/docs/release-process.md) - [Commits](video-dev/hls.js@v1.6.16...v1.7.0) --- updated-dependencies: - dependency-name: hls.js dependency-version: 1.7.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps [fastmcp](https://github.com/PrefectHQ/fastmcp) from 3.4.6 to 3.4.7. - [Release notes](https://github.com/PrefectHQ/fastmcp/releases) - [Changelog](https://github.com/PrefectHQ/fastmcp/blob/main/docs/changelog.mdx) - [Commits](PrefectHQ/fastmcp@v3.4.6...v3.4.7) --- updated-dependencies: - dependency-name: fastmcp dependency-version: 3.4.7 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
…sories The "Test & Deploy" CI run #570 (32071155482) failed at the "Dependency scan (pip-audit)" step with 4 known vulnerabilities in 2 packages, blocking an unrelated Dependabot PR (setup-uv 10.0.1): 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 Both are transitive deps surfaced by the PyPA advisory DB landing new advisories during a quiet window — no code changed. The existing constraint-dependencies block already pins cryptography>=48.0.1 to clear the older GHSA-537c-gmf6-5ccf; this bump raises the floor to >=50.0.0 to clear the three 2026-08 advisories and adds a new click>=8.3.3 constraint for PYSEC-2026-2132 (transitive via uvicorn). Side effect: forcing cryptography>=50.0.0 also advances clerk-backend-api 6.0.1 -> 7.0.0 (a MAJOR bump) because clerk 6.x cannot satisfy cryptography 50.0.0. The code uses only Clerk's stable auth surface (Clerk, authenticate_request, AuthenticateRequestOptions), and the full 699-test suite passes against clerk 7.0.0 + cryptography 50.0.0 + click 8.4.2. Noted in the constraint comment for the next maintainer. Verified locally: - uv run ruff check -> All checks passed - uv run pip-audit --strict -> No known vulnerabilities found - uv run pytest -v -> 699 passed
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
2 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.
CI fix for run #570 — pip-audit --strict failure
The "Test & Deploy" run #570 (32071155482) failed at the Dependency scan (pip-audit) step, blocking this Dependabot PR (setup-uv 10.0.1):
Root cause
New advisories landed in the PyPA Advisory DB (~2026-08) against two transitive dependencies that the project doesn't pin directly:
click 8.3.1— pulled in viauvicorncryptography 48.0.1— pulled in viaclerk-backend-api/authlibNo code changed; the scan just started failing on unrelated PRs. This is unrelated to the
setup-uvaction bump this PR is making.Fix
Raises the existing transitive constraint floor in
backend/pyproject.toml([tool.uv] constraint-dependencies) and regeneratesuv.lock:cryptography>=48.0.1→cryptography>=50.0.0(clears all 3 new advisories; 50.0.0 is the highest floor)click>=8.3.3constraint (PYSEC-2026-2132)Forcing
cryptography>=50.0.0also advancesclerk-backend-api6.0.1 → 7.0.0 (a MAJOR bump). Clerk 6.x cannot satisfy cryptography 50.0.0, so the resolver is forced to clerk 7.0.0. This is documented in the constraint comment. The code only touches Clerk's stable auth surface (Clerk,authenticate_request,AuthenticateRequestOptions), and the full suite passes against clerk 7.0.0 — but this deserves a look before merge since it touches the auth layer.Verified locally (sandbox, against this branch)
uv run ruff check→ All checks passeduv run pip-audit --strict→ No known vulnerabilities founduv run pytest -v→ 699 passedOnce merged into
dependabot/github_actions/astral-sh/setup-uv-10.0.1, the pip-audit gate on this PR will go green.— Hermes coder CI triage (automated)