Repository navigation
Conversation
Move the default branch onto the 26.08 upstream containers now that the
release has shipped to NGC.
- build.py upstream_container_version 26.07 -> 26.08; release_version and
triton_container_version stay on the 26.09dev train set at code freeze
- deployment charts, compose/perf docs, README and the openai frontend docs
move to the 26.08 container tag and the 2.72.0 semver
- qa/common/gen_qa_model_repository{,.py} defaults were still on the 26.08dev
train and 26.07 upstream; bring all three versions forward so they match
build.py's map
The gke-marketplace MAJOR_VERSION (2.67), chart appVersion (2.68),
TRITON_VERSION (2.73.0dev) and the build_wheel.py docstring examples are
deliberately left alone.
(cherry picked from commit 6fa22ae)
This was referenced Sep 1, 2026
Merged
mc-nv
marked this pull request as ready for review
September 1, 2026 19:19
Greptile SummaryThe PR advances main-branch release references and upstream dependencies to the 26.08 train while retaining the 26.09 development container and 2.73.0dev server versions.
Confidence Score: 5/5The PR appears safe to merge based on the reviewed version alignment, build migration, deployment defaults, and QA updates. The changed release references are consistently advanced, and no concrete build, runtime, deployment, or QA failure remains in the final review. Important Files Changed
Flowchart%%{init: {'theme': 'neutral'}}%%
flowchart LR
A[26.08 upstream containers] --> B[Build and SDK images]
A --> C[Deployment defaults]
A --> D[Documentation examples]
E[Manylinux Python] --> B
F[ORT 1.28 and ONNX opset 26] --> G[QA model generation]
B --> H[26.09dev Triton development image]
G --> H
Reviews (1): Last reviewed commit: "docs: add 26.08 rows to the release comp..." | Re-trigger Greptile |
yinggeh
approved these changes
Sep 1, 2026
mc-nv
deleted the
mchornyi/TRI-1691/before-ngc-release-advance-master-branch-to-next-upstream-release
branch
September 2, 2026 01:53
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does the PR do?
mainonto the 26.08 upstream containers now that the release has shipped to NGC.build.pymap:upstream_container_version26.07 -> 26.08, ORT 1.28.0, OpenVINO 2026.3.0, DCGM 4.6.1-1.release_version2.73.0dev andtriton_container_version26.09dev are kept - they are the next dev train, set at code freeze.Checklist
<commit_type>: <Title>Commit Type:
Check the conventional commit type
box here and add the label to the github PR.
Related PRs:
Where should the reviewer start?
build.pyDEFAULT_TRITON_VERSION_MAP— the split between adopted and deliberately-kept fields.Test plan:
Full CI run on the internal pipeline at
TRITON_CONTAINER_VERSION=26.09dev_user, withTRITON_NIGHTLY=1andTRITON_SBSA=1.Local verification: per-repo
pre-commit run --files <changed>passes with no auto-fixes.CI Pipeline ID:
Caveats:
TRITON_SERVER_MODEL_REPO_VERSIONderives fromTRITON_CONTAINER_VERSION, so26.09devmust exist on the share first.Background
Post-release step of the 26.08 train: the default branches move onto the same upstream containers as the just-released
r26.08, and pick up the fixes that landed only on the release branch while it stabilised.Related Issues: (use one of the action keywords Closes / Fixes / Resolves / Relates to)