chore: Update default branch to track 2.75.0 / 26.11

[mc-nv]

What does the PR do?

Advances main to track the next development release now that the 26.10 train is at code freeze.

• TRITON_VERSION: 2.74.0dev → 2.75.0dev

build.py DEFAULT_TRITON_VERSION_MAP already reads release_version 2.75.0dev / triton_container_version 26.11dev (#9000), so TRITON_VERSION is the only file still on the previous train. upstream_container_version is deliberately left alone; moving main onto the 26.10 upstream containers is a separate post-release step.

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.
• All template sections are filled out.

Commit Type:

Uses chore (mechanical version-tracking bump).

Related PRs:

• chore: Update dev, OpenVINO and DCGM versions #9000
• chore: Update default branch to track 1.60.0 / 26.11 model_analyzer#1040

Where should the reviewer start?

TRITON_VERSION.

Test plan:

Version-string-only change; validated by the standard CI build.

Caveats:

None. The 2.75.0 ↔ 26.11 pairing follows the mapping in build.py (2.73↔26.09, 2.74↔26.10).

Background

Routine code-freeze step: once a release branch is cut, main advances to the next dev version so post-freeze work targets the upcoming train.

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

• Resolves: TRI-1975

[greptile-apps]

Confidence Score: 5/5

[Low impact] This version-only change appears safe to merge.

Summary

Updates TRITON_VERSION from 2.74.0dev to 2.75.0dev.

• The server now identifies its development version as 2.75.0dev.

_{Reviews (1) · Last reviewed commit: "chore: Update default branch to track 2...." · Reviewed by Greptile}