Update python

[renovate]

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
PyGithub	==2.4.0 → ==2.9.1
aiosignal	==1.3.1 → ==1.4.0
annotated-types (changelog)	==0.6.0 → ==0.7.0
anyio (changelog)	==4.3.0 → ==4.14.2
charset-normalizer (changelog)	==3.3.2 → ==3.4.9
cloudpickle	==3.0.0 → ==3.1.2
cmake	~=3.29.3 → ~=3.31.10
cmake	==3.29.3 → ==3.31.10
dnspython	==2.6.1 → ==2.8.0
einops	==0.8.0 → ==0.8.2
email-validator	==2.1.1 → ==2.3.0
fastapi (changelog)	~=0.111.0 → ~=0.139.2
fastapi (changelog)	~=0.115.0 → ~=0.139.2
fastapi (changelog)	==0.115.0 → ==0.139.2
fastapi (changelog)	==0.111.0 → ==0.139.2
fastapi-cli (changelog)	==0.0.5 → ==0.0.32
fastapi-cli (changelog)	==0.0.3 → ==0.0.32
frozenlist	==1.4.1 → ==1.8.0
fsspec (changelog)	==2024.3.1 → ==2024.12.0
httpcore	==1.0.5 → ==1.0.9
httptools	==0.6.1 → ==0.8.0
httpx (changelog)	==0.27.0 → ==0.28.1
huggingface-hub	==0.26.3 → ==0.36.2
joblib	==1.4.2 → ==1.5.3
jsonschema (changelog)	==4.22.0 → ==4.26.0
lark	==1.2.2 → ==1.3.1
lark	==1.1.9 → ==1.3.1
llama-cpp-python (changelog)	==0.3.8 → ==0.3.34
llama-cpp-python (changelog)	==0.3.16 → ==0.3.34
llvmlite (source)	==0.44.0 → ==0.48.0
llvmlite (source)	==0.42.0 → ==0.48.0
lm-format-enforcer	==0.9.8 → ==0.11.3
lm-format-enforcer	==0.10.11 → ==0.11.3
lm-format-enforcer	==0.10.9 → ==0.11.3
lm-format-enforcer	==0.10.6 → ==0.11.3
mpmath	==1.3.0 → ==1.4.1
networkx	==3.3 → ==3.6.1
ninja	~=1.11.1.1 → ~=1.13.0.0
ninja	==1.11.1.1 → ==1.13.0
numba	==0.61.2 → ==0.66.0
numba	==0.59.1 → ==0.66.0
nvidia-cudnn-cu12	==9.1.0.70 → ==9.24.0.43
nvidia-cudnn-cu12	==9.10.2.21 → ==9.24.0.43
nvidia-curand-cu12	==10.3.2.106 → ==10.3.10.19
nvidia-cusolver-cu12	==11.4.5.107 → ==11.7.5.82
nvidia-cusparse-cu12	==12.1.0.106 → ==12.5.10.65
nvidia-ml-py	~=12.550.52 → ~=12.575.51
nvidia-ml-py	~=12.560.30 → ~=12.575.51
nvidia-ml-py	==12.560.30 → ==12.575.51
nvidia-nvjitlink-cu12	==12.4.127 → ==12.9.86
nvidia-nvjitlink-cu12	==12.8.93 → ==12.9.86
nvidia-nvtx-cu12	==12.1.105 → ==12.9.79
openai	~=1.28.1 → ~=1.109.1
openai	~=1.99.1 → ~=1.109.1
openai	==1.56.0 → ==1.109.1
openai	==1.99.1 → ==1.109.1
outlines	==0.0.34 → ==0.2.3
outlines	~=0.1.11 → ~=0.2.3
outlines	==0.1.11 → ==0.2.3
outlines	==0.0.46 → ==0.2.3
outlines	==1.2.5 → ==1.3.1
outlines-core	==0.2.11 → ==0.2.14
packaging	==24.0 → ==24.2
prometheus-client	==0.20.0 → ==0.25.0
prometheus-fastapi-instrumentator	~=7.0.0 → ~=7.1.0
prometheus-fastapi-instrumentator	==7.0.0 → ==7.1.0
prometheus_client	~=0.20.0 → ~=0.25.0
pydantic (changelog)	~=2.7.1 → ~=2.13.4
pydantic (changelog)	~=2.11.7 → ~=2.13.4
pydantic (changelog)	==2.10.0 → ==2.13.4
pydantic (changelog)	==2.11.7 → ==2.13.4
pydantic-core	==2.27.0 → ==2.47.0
pydantic-core	==2.33.2 → ==2.47.0
pynvml	==11.5.0 → ==11.5.3
pyyaml (source)	==6.0.1 → ==6.0.3
referencing (changelog)	==0.35.1 → ==0.37.0
regex	==2024.5.10 → ==2024.11.6
rich	==13.7.1 → ==13.9.4
rpds-py	==0.18.1 → ==0.30.0
safetensors	==0.4.3 → ==0.8.0
scipy	==1.13.0 → ==1.18.0
sympy (source)	==1.13.1 → ==1.14.0
sympy (source)	==1.13.3 → ==1.14.0
tiktoken (changelog)	==0.6.0 → ==0.13.0
tiktoken (changelog)	~=0.6.0 → ~=0.13.0
tokenizers	~=0.19.1 → ~=0.23.1
tokenizers	~=0.21.1 → ~=0.23.1
tokenizers	==0.21.0 → ==0.23.1
tokenizers	==0.20.3 → ==0.23.1
tokenizers	==0.21.1 → ==0.23.1
tqdm (changelog)	==4.66.4 → ==4.68.4
triton	==2.3.0 → ==2.3.1
triton	==3.2.0 → ==3.7.1
triton	==3.1.0 → ==3.7.1
triton	==3.4.0 → ==3.7.1
typer (changelog)	==0.12.3 → ==0.27.0
typing-extensions (changelog)	==4.12.2 → ==4.16.0
typing_extensions (changelog)	~=4.11.0 → ~=4.16.0
typing_extensions (changelog)	~=4.12.2 → ~=4.16.0
uvicorn (changelog)	~=0.29.0 → ~=0.51.0
uvicorn (changelog)	==0.29.0 → ==0.51.0
uvloop	==0.19.0 → ==0.22.1
watchfiles (changelog)	==0.21.0 → ==0.24.0
xformers	==0.0.26.post1 → ==0.0.35
xformers	==0.0.32.post1 → ==0.0.35
xformers	==0.0.29.post2 → ==0.0.35
xformers	==0.0.28.post3 → ==0.0.35

---

Release Notes

pygithub/pygithub (PyGithub)

v2.9.1

Compare Source

Bug Fixes

• Fix getting release by tag in lazy mode by @​EnricoMi in PyGithub/PyGithub#3469

Full Changelog: PyGithub/PyGithub@v2.9.0...v2.9.1

v2.9.0

Compare Source

Notable changes

Lazy PyGithub objects

The notion of lazy objects has been added to some PyGithub classes in version 2.6.0. This release now makes all CompletableGithubObjects optionally lazy (if useful). See PyGithub/PyGithub#3403 for a complete list.

In lazy mode, getting a PyGithub object does not send a request to the GitHub API. Only accessing methods and properties sends the necessary requests to the GitHub API:

# Use lazy mode
g = Github(auth=auth, lazy=True)

# these method calls do not send requests to the GitHub API
user = g.get_user("PyGithub")    # get the u

> ✂ **Note**
> 
> PR body was truncated to here.


</details>

---

### Configuration

📅 **Schedule**: (in timezone America/Toronto)

- Branch creation
  - Between 12:00 AM and 12:59 AM, on day 1 and 15 of the month (`* 0 1,15 * *`)
- Automerge
  - At any time (no schedule defined)

🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied.

♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 **Immortal**: This PR will be recreated if closed unmerged. Get [config help](https://redirect.github.com/renovatebot/renovate/discussions) if that's undesired.

---

 - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box

---

This PR was generated by [Mend Renovate](https://mend.io/renovate/). View the [repository job log](https://developer.mend.io/github/redhat-ai-dev/developer-images).
<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0My4xODUuMSIsInVwZGF0ZWRJblZlciI6IjQzLjI2NS4xIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJyZW5vdmF0ZWJvdCJdfQ==-->

[renovate]

⚠️ Artifact update problem

Renovate failed to update artifacts related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: model-servers/vllm/0.11.0/Pipfile.lock

Command failed: pipenv lock
Locking  dependencies...
CRITICAL:pipenv.patched.pip._internal.resolution.resolvelib.factory:Cannot 
install -r /tmp/pipenv-nb_336hu-requirements/pipenv-muwiroip-constraints.txt 
(line 30) and filelock~=3.14.0 because these package versions have conflicting 
dependencies.
CRITICAL:pipenv.patched.pip._internal.resolution.resolvelib.factory:
The conflict is caused by:
    The user requested filelock~=3.14.0
    vllm 0.11.0 depends on filelock>=3.16.1
Additionally, some packages in these conflicts have no matching distributions 
available for your environment:
    filelock
To fix this you could try to:
1. loosen the range of package versions you've specified
2. remove package versions to allow pip to attempt to solve the dependency 
conflict
Your dependencies could not be resolved. You likely have a mismatch in your 
sub-dependencies.
You can use $ pipenv run pip install <requirement_name> to bypass this 
mechanism, then run $ pipenv graph to inspect the versions actually installed in
the virtualenv.
Hint: try $ pipenv lock --pre if it is a pre-release dependency.
Hint: try $ pipenv lock --verbose to see the full dependency resolution output.
ERROR: ResolutionImpossible: for help visit 
https://pip.pypa.io/en/latest/topics/dependency-resolution/#dealing-with-depende
ncy-conflicts
The conflict is caused by:
    The user requested filelock~=3.14.0
    vllm 0.11.0 depends on filelock>=3.16.1

Hint: Re-run with --verbose to see the full dependency resolution output and 
identify which packages are in conflict.
Traceback (most recent call last):
  File 
"/opt/containerbase/tools/pipenv/2026.6.2/3.11.15/lib/python3.11/site-packages/p
ipenv/routines/lock.py", line 94, in do_lock
    venv_resolve_deps(
  File 
"/opt/containerbase/tools/pipenv/2026.6.2/3.11.15/lib/python3.11/site-packages/p
ipenv/utils/resolver.py", line 1467, in venv_resolve_deps
    c = resolve(cmd, st, project=project)
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File 
"/opt/containerbase/tools/pipenv/2026.6.2/3.11.15/lib/python3.11/site-packages/p
ipenv/utils/resolver.py", line 1240, in resolve
    raise ResolutionFailure("Failed to lock Pipfile.lock!")
pipenv.exceptions.ResolutionFailure: ERROR: Failed to lock Pipfile.lock!

File name: model-servers/vllm/0.6.4/Pipfile.lock

Command failed: pipenv lock
Locking  dependencies...
CRITICAL:pipenv.patched.pip._internal.resolution.resolvelib.factory:Cannot 
install -r /tmp/pipenv-efzgp70n-requirements/pipenv-9udgywiv-constraints.txt 
(line 26) and torch==2.3.0+cu121 because these package versions have conflicting
dependencies.
CRITICAL:pipenv.patched.pip._internal.resolution.resolvelib.factory:
The conflict is caused by:
    The user requested torch==2.3.0+cu121
    xformers 0.0.35 depends on torch>=2.10
Additionally, some packages in these conflicts have no matching distributions 
available for your environment:
    torch
To fix this you could try to:
1. loosen the range of package versions you've specified
2. remove package versions to allow pip to attempt to solve the dependency 
conflict
Your dependencies could not be resolved. You likely have a mismatch in your 
sub-dependencies.
You can use $ pipenv run pip install <requirement_name> to bypass this 
mechanism, then run $ pipenv graph to inspect the versions actually installed in
the virtualenv.
Hint: try $ pipenv lock --pre if it is a pre-release dependency.
Hint: try $ pipenv lock --verbose to see the full dependency resolution output.
ERROR: ResolutionImpossible: for help visit 
https://pip.pypa.io/en/latest/topics/dependency-resolution/#dealing-with-depende
ncy-conflicts
The conflict is caused by:
    The user requested torch==2.3.0+cu121
    xformers 0.0.35 depends on torch>=2.10

Hint: Re-run with --verbose to see the full dependency resolution output and 
identify which packages are in conflict.
Traceback (most recent call last):
  File 
"/opt/containerbase/tools/pipenv/2026.6.2/3.11.15/lib/python3.11/site-packages/p
ipenv/routines/lock.py", line 94, in do_lock
    venv_resolve_deps(
  File 
"/opt/containerbase/tools/pipenv/2026.6.2/3.11.15/lib/python3.11/site-packages/p
ipenv/utils/resolver.py", line 1467, in venv_resolve_deps
    c = resolve(cmd, st, project=project)
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File 
"/opt/containerbase/tools/pipenv/2026.6.2/3.11.15/lib/python3.11/site-packages/p
ipenv/utils/resolver.py", line 1240, in resolve
    raise ResolutionFailure("Failed to lock Pipfile.lock!")
pipenv.exceptions.ResolutionFailure: ERROR: Failed to lock Pipfile.lock!

File name: model-servers/vllm/0.6.6/Pipfile.lock

Command failed: pipenv lock
Locking  dependencies...
CRITICAL:pipenv.patched.pip._internal.resolution.resolvelib.factory:Cannot 
install -r /tmp/pipenv-bc0ygngg-requirements/pipenv-_nvuntt4-constraints.txt 
(line 27) and transformers~=4.40.2 because these package versions have 
conflicting dependencies.
CRITICAL:pipenv.patched.pip._internal.resolution.resolvelib.factory:
The conflict is caused by:
    The user requested transformers~=4.40.2
    vllm 0.6.6 depends on transformers>=4.45.2
Additionally, some packages in these conflicts have no matching distributions 
available for your environment:
    transformers
To fix this you could try to:
1. loosen the range of package versions you've specified
2. remove package versions to allow pip to attempt to solve the dependency 
conflict
Your dependencies could not be resolved. You likely have a mismatch in your 
sub-dependencies.
You can use $ pipenv run pip install <requirement_name> to bypass this 
mechanism, then run $ pipenv graph to inspect the versions actually installed in
the virtualenv.
Hint: try $ pipenv lock --pre if it is a pre-release dependency.
Hint: try $ pipenv lock --verbose to see the full dependency resolution output.
ERROR: ResolutionImpossible: for help visit 
https://pip.pypa.io/en/latest/topics/dependency-resolution/#dealing-with-depende
ncy-conflicts
The conflict is caused by:
    The user requested transformers~=4.40.2
    vllm 0.6.6 depends on transformers>=4.45.2

Hint: Re-run with --verbose to see the full dependency resolution output and 
identify which packages are in conflict.
Traceback (most recent call last):
  File 
"/opt/containerbase/tools/pipenv/2026.6.2/3.11.15/lib/python3.11/site-packages/p
ipenv/routines/lock.py", line 94, in do_lock
    venv_resolve_deps(
  File 
"/opt/containerbase/tools/pipenv/2026.6.2/3.11.15/lib/python3.11/site-packages/p
ipenv/utils/resolver.py", line 1467, in venv_resolve_deps
    c = resolve(cmd, st, project=project)
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File 
"/opt/containerbase/tools/pipenv/2026.6.2/3.11.15/lib/python3.11/site-packages/p
ipenv/utils/resolver.py", line 1240, in resolve
    raise ResolutionFailure("Failed to lock Pipfile.lock!")
pipenv.exceptions.ResolutionFailure: ERROR: Failed to lock Pipfile.lock!

File name: model-servers/vllm/0.8.4/Pipfile.lock

Command failed: pipenv lock
Locking  dependencies...
CRITICAL:pipenv.patched.pip._internal.resolution.resolvelib.factory:Cannot 
install -r /tmp/pipenv-2fjf1qgo-requirements/pipenv-m4o3mqzx-constraints.txt 
(line 23) and torch==2.3.0+cu121 because these package versions have conflicting
dependencies.
CRITICAL:pipenv.patched.pip._internal.resolution.resolvelib.factory:
The conflict is caused by:
    The user requested torch==2.3.0+cu121
    vllm-flash-attn 2.6.2 depends on torch==2.4.0
Additionally, some packages in these conflicts have no matching distributions 
available for your environment:
    torch
To fix this you could try to:
1. loosen the range of package versions you've specified
2. remove package versions to allow pip to attempt to solve the dependency 
conflict
Your dependencies could not be resolved. You likely have a mismatch in your 
sub-dependencies.
You can use $ pipenv run pip install <requirement_name> to bypass this 
mechanism, then run $ pipenv graph to inspect the versions actually installed in
the virtualenv.
Hint: try $ pipenv lock --pre if it is a pre-release dependency.
Hint: try $ pipenv lock --verbose to see the full dependency resolution output.
ERROR: ResolutionImpossible: for help visit 
https://pip.pypa.io/en/latest/topics/dependency-resolution/#dealing-with-depende
ncy-conflicts
The conflict is caused by:
    The user requested torch==2.3.0+cu121
    vllm-flash-attn 2.6.2 depends on torch==2.4.0

Hint: Re-run with --verbose to see the full dependency resolution output and 
identify which packages are in conflict.
Traceback (most recent call last):
  File 
"/opt/containerbase/tools/pipenv/2026.6.2/3.11.15/lib/python3.11/site-packages/p
ipenv/routines/lock.py", line 94, in do_lock
    venv_resolve_deps(
  File 
"/opt/containerbase/tools/pipenv/2026.6.2/3.11.15/lib/python3.11/site-packages/p
ipenv/utils/resolver.py", line 1467, in venv_resolve_deps
    c = resolve(cmd, st, project=project)
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File 
"/opt/containerbase/tools/pipenv/2026.6.2/3.11.15/lib/python3.11/site-packages/p
ipenv/utils/resolver.py", line 1240, in resolve
    raise ResolutionFailure("Failed to lock Pipfile.lock!")
pipenv.exceptions.ResolutionFailure: ERROR: Failed to lock Pipfile.lock!