chore(post-release): Update default branches post-26.07

[mc-nv]

What does the PR do?

26.07 has released to NGC, so main moves onto the same upstream containers as the
just-released r26.07 branch. Bumps upstream_container_version, NGC image tags, deploy
chart versions, docs, and QA model-repository defaults from 26.06/2.70.0 to
26.07/2.71.0, and carries forward the 26.07 compatibility-matrix rows.

The dev-train values are deliberately untouched: TRITON_VERSION stays 2.72.0dev, and
build.py's release_version / triton_container_version stay 2.72.0dev / 26.08dev
(set at code freeze). Also frozen, matching every prior cycle: build_and_push.sh
MAJOR_VERSION=2.67, gke Chart.yaml appVersion "2.68", and the semver examples in
src/python/build_wheel.py.

The diff matches the previous cycle's post: Update default branch post-26.05 (#8804)
file-for-file and line-for-line, with one addition: qa/L2_build_presets/README.md, which
did not exist then.

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:

• build(dependencies): update Tomca version (#912) client#913
• chore(post-release): Update default branches post-26.07 tutorials#165

Where should the reviewer start?

build.py — confirm only upstream_container_version moved inside
DEFAULT_TRITON_VERSION_MAP and the two dev-train fields are unchanged. Everything else is
a mechanical tag/semver replacement.

Test plan:

• git grep "26\.06" returns only the historical rows in docs/introduction/compatibility.md.

• The [!WARNING] main-branch notice at the top of README.md is intact, with only its
  version number and NGC tag updated.

• git diff --stat matches 258a8cbcf per file and per line count.

• pre-commit run --files <changed> passes.

• CI Pipeline ID: 60058404

Caveats:

tutorials/Build_Guide/RHEL_Manylinux/README.md still targets 2.69.0 / NGC 26.05. It is
main-only (added after the r26.07 cut) so no cherry-pick reaches it, and its 26.05
references are coupled to a stated CUDA / TensorRT / PyTorch tuple — bumping the NGC number
alone would make that tuple wrong. Left for a separate doc refresh.

Background

Release step "[Before NGC Release] Advance master branch to next upstream release".
Follows post: Update default branch post-26.05 (#8804) and
post(TRI-1431): advance main with r26.06 upstream-tracking cherry-picks (#8861).

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

• Resolves: TRI-1601

^{CI (internal): [#60058404](http://tritonserver.local/ci/pipelines/60058404)}

[greptile-apps]

Greptile Summary

Advances main-branch release defaults to Triton 2.71.0 and NGC 26.07.

• Updates upstream container, deployment image, chart, and model-repository defaults.
• Refreshes documentation and examples to reference release 26.07.
• Adds 26.07 compatibility-matrix entries and updates QA model-generation defaults.

Confidence Score: 5/5

The PR appears safe to merge, with the release, container, deployment, documentation, and QA defaults advanced consistently.

The changed values follow the established post-release pairing of the 2.72.0dev development train with released 26.07 upstream artifacts, and no concrete changed-code failure was identified.

Important Files Changed

Filename	Overview
build.py	Updates only the upstream container default to 26.07 while preserving the 2.72.0dev and 26.08dev development-train values.
deploy/gke-marketplace-app/server-deployer/chart/triton/values.yaml	Coherently advances the sample-model path, published version, and Triton image tag to the 26.07 release.
deploy/gke-marketplace-app/server-deployer/schema.yaml	Aligns Marketplace metadata and the default model repository with the new chart values.
docs/introduction/compatibility.md	Adds compatibility rows for the 26.07 TensorRT-LLM, vLLM, and ONNX Runtime images.
qa/common/gen_qa_model_repository	Makes 26.07 the default release used to select model-generation containers and output paths.
qa/common/gen_jetson_trt_models	Advances the default Jetson TensorRT model-generation release to 26.07.

_{Reviews (1): Last reviewed commit: "docs: Update compatibility md (#8902)" | Re-trigger Greptile}