chore(versions): align tutorials examples with 26.06 release train (cherry-pick)#152
Open
mc-nv wants to merge 1 commit into
Open
chore(versions): align tutorials examples with 26.06 release train (cherry-pick)#152mc-nv wants to merge 1 commit into
mc-nv wants to merge 1 commit into
Conversation
) * fix(deps): bump transformers/torch/ray to mitigate CVEs (TRI-1421) Bumps in tutorials/ examples to patched versions: * style: black reformat for Quick_Deploy/PyTorch/export.py Collapses an over-wrapped multi-line expression onto a single line to satisfy black. Picked up by pre-commit run --all-files; not otherwise related to TRI-1421. * chore(versions): bump tutorials examples to 26.06 release Aligns container references and pinned client versions with the 26.06 release (release_version 2.70.0, triton_container_version 26.06, upstream_container_version 26.05 per server/build.py): - nvcr.io/nvidia/tritonserver XX.XX-* -> 26.06-* (covers -py3, -py3-sdk, -vllm-python-py3, -trtllm-python-py3 across Conceptual_Guide, Quick_Deploy, Popular_Models_Guide, Feature_Guide, Deployment/Kubernetes, Triton_Inference_Server_Python_API) - nvcr.io/nvidia/pytorch 23.05-py3 -> 26.05-py3 - nvcr.io/nvidia/tensorflow 24.04-tf2-py3 -> 26.05-tf2-py3 - tritonclient 2.47.0 -> 2.70.0 (kafka-io example) - Internal image tag triton-python-api:r24.08 -> r26.06 in Triton_Inference_Server_Python_API/README.md Placeholder references (yy.mm, xx.yy, <yy.mm>) intentionally left unchanged. Examples that span multiple release trains may need follow-up code adjustments to keep working against the new SDK. * fix(deps): correct tritonclient pin to 2.69.0 (latest on PyPI) The 26.06 server build reports version 2.70.0 but the tritonclient wheel for 2.70.0 has not been published to PyPI yet (latest published is 2.69.0). Pinning the kafka-io example to 2.69.0 so pip install -r requirements.txt resolves today. Bump to 2.70.0 once the wheel ships. * fix(deps): bump sentencepiece pin to 0.2.1 for Python 3.12 wheel The 26.06-py3 tritonserver image ships Python 3.12. sentencepiece 0.1.99 has no cp312 wheel and pip falls back to building from source, which fails inside the container. 0.2.1 has a cp312 wheel and installs cleanly. Verified by building the Dockerfile against the staged tritonserver:26.06-py3 image. * fix(versions): bump 24.08 -> 26.06 in Python_API build.sh / Dockerfile Caught by the staged-image test pass: build.sh hardcoded BASE_IMAGE_TAG_IDENTITY/DIFFUSION, the default TAG slug, and the StableDiffusion sub-build references at 24.08. docker/Dockerfile ARG BASE_IMAGE_TAG also defaulted to 24.08-py3. Aligned all to 26.06. The earlier sweep missed these because the regex looked for nvcr.io / tritonserver: prefixes; the literals lived as bare shell-variable values.
This was referenced Jun 27, 2026
yinggeh
approved these changes
Jun 27, 2026
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.
What does the PR do?
Cherry-picks
d4745c1fromr26.06to advancemainpost-26.05 toward the 26.07dev_user container train (tracks upstream 26.06).Reviewer note — mixed content: the commit bundles two changes:
main).tritonserver:26.06-*,pytorch:26.05-py3,tritonclient 2.70.0). Onmainthis is a regression —mainshould track newer (26.07dev/26.07).Please decide whether to split this into two follow-up commits before merge.
Related PRs:
Test plan:
Caveats:
mainwhile keeping the CVE bump.Related Issues: