[mc-nv]

What does the PR do?

• Advance main onto the 26.10 upstream containers: build.py upstream and cuda-dl-base versions, plus README, deploy, docs and QA version strings (2.73.0 → 2.74.0, 26.09 → 26.10).
• Add 26.10 rows to compatibility.md; sync THIRD-PARTY-NOTICES.txt from r26.10.
• Dev train (2.75.0dev / 26.11dev) and the README main-branch warning are unchanged.

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): Align tutorials with 26.10 release train tutorials#178
• 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: 4/5

[Medium impact] The release update reaches build defaults, deployment targets, and guidance across several Triton workflows.

The PR appears safe to merge, with a non-blocking Fleet Command chart-version fix recommended.

Findings

1.  Chart version stays unchanged ▶

Summary

Advances build upstreams and release examples to 26.10 while keeping the 2.75.0dev / 26.11dev development train unchanged.

• Main-branch builds and QA model generation use upstream 26.10.
• Deployment defaults and examples point to Triton 26.10.
• Release guides and compatibility tables describe Triton 26.10.

_{Reviews (1) · Last reviewed commit: "docs: Add third-party notices for 26.10 ..." · Reviewed by Greptile}

[greptile-apps]

Chart version stays unchanged

The Fleet Command chart now serves Triton 2.74.0, but its chart version remains 1.4.0. This gives two different chart contents the same package version, so consumers cannot distinguish this update by version. The file's instructions call for a minor-version increase when updating Triton. Bump version to 1.5.0.