Allow Pillow 13 in inference-sdk
Maintainers usually reply within 1 day
Nobody has claimed this yet.
- #3342 by @voropaevv — closed without merging
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 80/100
Research direction
Start with requirements/requirements.sdk.http.txt and review the Pillow constraint for inference-sdk. Check the SDK’s image encoding path for compatibility with Pillow 13, then run the relevant dependency resolution and SDK tests. Done means Pillow 13 can be installed with inference-sdk and the supported constraint is updated.
Written by the indexing model from the issue text.
Description
Search before asking
- I have searched the Inference issues and found no similar bug report.
Bug
Hi,
inference-sdk pins pillow>=12.3.0,<13.0.0 (requirements/requirements.sdk.http.txt, still the case in 1.8.4 and on main). Pillow 13.0.0 fixes several security issues in 12.x, including CVE-2026-96639 and CVE-2026-112398 / CVE-2026-112403 (critical), plus CVE-2026-112393 and CVE-2026-112900.
With the cap in place, projects that depend on inference-sdk can't upgrade Pillow without overriding your constraint. Could you relax the upper bound to <14 (or bump the minimum to >=13.0.0)? The 13.0 breaking changes (removal of Image._show, get_child_images moved to ImageFile, I-mode PNG saving) don't seem to affect the SDK's encoding path, but you'd know better.
Thanks!
Environment
inference-sdk 1.8.4, Python 3.12
Minimal Reproducible Example
No solution found for uv pip compile with inference-sdk and pillow>=13.0.0
Additional
No response
Are you willing to submit a PR?
- Yes I'd like to help by submitting a PR!
- Dominant language
- Python
- Stars
- 2.5k
- Forks
- 340
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 92
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from roboflow/inference
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
roboflow/inference#3173 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
roboflow/inference#2993 · 2 comments ·
Maintainers usually reply within 1 day
-
Add context manager (__enter__ / __exit__) support to InferencePipelinePossibly taken @KushagraKanaujia claimed this 67 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
roboflow/inference#2744 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
roboflow/inference#1913 · 1 comment · 2 reactions ·
Maintainers usually reply within 1 day
-
onnxruntime CoreML execution provider leaks ~70-78 KB per inference on macOS (RF-DETR default config)Possibly taken @Nishant-ZFYII claimed this 14 days ago. Open
Difficulty 4/5 3-5 days Newbie friendliness 35/100
roboflow/inference#3302 · 13 comments ·
Maintainers usually reply within 1 day
All issues in roboflow/inference
Similar issues
-
area:core-platform effort:S priority:P3 risk:night-safe status:ready type:test
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
randomparity/kdive#3620 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
FinanceFlash/unvibecode#760 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
google-research/google-research#3470 ·
Maintainers usually reply within 21 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
mrvautin/ha-workouts#11 ·