Skip to content

chore(deps): bump pytest, diffusers and transformers pins to clear Dependabot alerts - #2854

Open
bhimrazy wants to merge 2 commits into
Lightning-AI:mainfrom
bhimrazy:chore/bump-vulnerable-test-deps
Open

bhimrazy wants to merge 2 commits into
Lightning-AI:mainfrom
bhimrazy:chore/bump-vulnerable-test-deps

Conversation

@bhimrazy

@bhimrazy bhimrazy commented Oct 13, 2026 •

Copy link
Copy Markdown
Collaborator

What does this PR do?

Bumps the test/CI dependency pins that have open Dependabot alerts and don't need a breaking upgrade. Clears 13 of the 42 open alerts.

  • pytest 8.4.2 → 9.1.1 (GHSA-6w46-j5rx-g56g)
  • diffusers 0.35.1 → 0.38.0 (GHSA-7wx4-6vff-v64p, GHSA-98h9-4798-4q5v)
  • transformers 4.52.4 → 4.55.4 in requirements/coverage.txt, matching requirements/test.txt (ReDoS advisories, fixed in 4.53)
  • Drop the trailing comma in single-name parametrize argnames ("device," → "device"). pytest 9 reads it as a tuple of names and fails collection.
Why diffusers 0.38.0 and not the latest

diffusers 0.39+ requires huggingface-hub>=1.x, and transformers 4.x requires huggingface-hub<1.0. 0.38.0 is the first patched release that still resolves alongside transformers 4.55.4.

Not in this PR: the remaining 25 transformers alerts

These need transformers ≥5.10, a major upgrade that touches thunder/recipes/hf_transformers.py, thunder/benchmarks/benchmark_inference.py (HybridChunkedCache) and the HF tests, so it should be a separate PR. GHSA-x9r9-c232-4q39 has no fix for 4.x. transformers is only a test, benchmark and example dependency, not part of requirements/base.txt.

…pendabot alerts

- pytest 8.4.2 -> 9.1.1 (GHSA-6w46-j5rx-g56g)
- diffusers 0.35.1 -> 0.38.0 (GHSA-7wx4-6vff-v64p, GHSA-98h9-4798-4q5v);
  0.39+ needs huggingface-hub>=1.x, which transformers 4.x rejects
- transformers 4.52.4 -> 4.55.4 in coverage requirements, matching test.txt
  (ReDoS advisories fixed in 4.53)
- drop trailing commas in single-name parametrize argnames, which pytest 9
  parses as a tuple of names and fails collection on
Touching examples/coverage/* triggers the jit coverage workflow.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant