[mc-nv]

What does the PR do?

• Align examples with the 26.10 release train (picked from r26.10: chore(doc,versions): Update README and Versions for 26.10 #176, chore: Bump click and transformers versions #177).
• trtllm images intentionally stay on 26.07, as on r26.10.

Checklist

• PR title reflects the change and is of format <commit_type>: <Title>
• Changes are described in the pull request.
• Related issues are referenced.
• Populated github labels field
• Added test plan and verified test passes.
• Verified that the PR passes existing CI.
• Verified copyright is correct on all changed files.
• Added succinct git squash message before merging ref.
• All template sections are filled out.
• Optional: Additional screenshots for behavior/output changes with before/after.

Commit Type:

Check the conventional commit type
box here and add the label to the github PR.

• build
• ci
• docs
• feat
• fix
• perf
• refactor
• revert
• style
• test

Related PRs:

• chore(post-release): Advance main to 26.10 upstreams server#9049
• merge_requests!1923

Where should the reviewer start?

Test plan:

• CI Pipeline ID:

Caveats:

Background

Related Issues: (use one of the action keywords Closes / Fixes / Resolves / Relates to)

• Resolves: TRI-1990

[greptile-apps]

Confidence Score: 5/5

[Medium impact] The PR appears safe to merge; no actionable regression was found.

Summary

Updates tutorial images, build tags, and documentation for the 26.10 release.

• Inference tutorials use Triton 26.10 images.
• Stable Diffusion builds and runs use Triton 26.10 images.
• Python API images and Kafka I/O setup use updated release versions.
• TensorRT-LLM deployment images stay on 26.07 as the EKS tools pod moves to 26.10.

_{Reviews (1) · Last reviewed commit: "chore: Bumping default versions (#177)" · Reviewed by Greptile}