GeezerVison

@jonny-norwine I'd merge this at 3f28707. It follows #5876, which excluded 1.82.7 and 1.82.8 the same way, and the specifier drops only 1.107.0. The rc builds that the SafeDep write-up calls clean still resolve.

$ python3 spec_check.py   # packaging SpecifierSet(...).contains(v, prereleases=True) on the litellm extra in setup.py at 3f28707
setup.py at 3f28707: litellm>=1.77.5,!=1.82.7,!=1.82.8,!=1.107.0
1.82.7 False
1.106.2 True
1.107.0rc2 True
1.107.0 False
1.107.1 True

$ curl -s https://pypi.org/pypi/litellm/json | python3 releases.py   # the releases map, 2026-10-21
1.82.7 absent
1.82.8 absent
1.107.0 absent
latest 1.106.2

PyPI has already removed 1.107.0, so a fresh resolve from pypi.org cannot pick it. The exclusion still guards mirrors that cached it before the removal, and it cleans up the range a scanner reads from your poetry.lock.

@sentrivana this is one line in setup.py. Could it go out in the next patch release, so that lock files pick up the exclusion?

Thank you @jonny-norwine!