[devin-ai-integration]

What does the PR do?

• Cherry-pick of build: Update ONNX Runtime version #9053: ort_version 1.31.1
• TRITON_VERSION / build.py: 2.75.0, container + upstream 26.11, cuda_dl_base_version 26.11-cuda13.5 (also Dockerfile.sdk)
• README: main-branch banner dropped, links → r26.11
• 26.10 / 2.74.0 → 26.11 / 2.75.0 in deploy, Helm, docs, QA defaults
• compatibility.md: 26.11 ORT row

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
• chore
• ci
• docs
• feat
• fix
• perf
• refactor
• revert
• style
• test

Related PRs:

• chore(doc,versions): Update README and Versions for 26.11 model_analyzer#1045
• chore(doc,versions): Update README and Versions for 26.11 tutorials#179
• chore(versions): Update version for 26.11 perf_analyzer#477
• build: Update ONNX Runtime version #9053

Where should the reviewer start?

build.py, TRITON_VERSION, README.md, docs/introduction/compatibility.md, qa/common/gen_qa_model_repository

Test plan:

Version/doc strings only; pre-commit passes. GitHub checks don't build containers; that is covered by the GitLab 26.11-devel pipeline.

• CI Pipeline ID: n/a

Caveats:

No 26.11 vLLM row in compatibility.md; it needs values from the 26.11 stage image.

Background

26.11 release-branch bump; same file set as #9016 (26.10).

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

• Resolves: TRI-2072

[devin-ai-integration]

I'll fix CI failures and address comments from users with write access. I'll skip comments containing "(aside)".

• Disable automatic comment, CI, and merge conflict monitoring

[greptile-apps]

Confidence Score: 5/5

[Medium impact] The PR appears safe to merge; no actionable issues were found.

Summary

Updates the release branch to Triton 2.75.0 and container release 26.11.

• Triton builds now use the 26.11 release settings.
• Deployment templates now point to Triton 26.11.
• Release guides and examples now show Triton 26.11.
• QA model generation now defaults to the 26.11 release.

Acknowledged choices:

• devin-ai-integration[bot] explicitly chose Fleet Command chart version 2.75.0.
• devin-ai-integration[bot] deferred the November vLLM compatibility row until values are available from the stage image.

Review used source inspection; no container builds or runtime tests were run.

_{Reviews (1) · Last reviewed commit: "chore(doc,versions): Update README and V..." · Reviewed by Greptile}