Skip to content

chore(post-release): advance main to 26.08 upstreams - #8949

Merged
mc-nv merged 3 commits into
mainfrom
mchornyi/TRI-1691/before-ngc-release-advance-master-branch-to-next-upstream-release
Sep 2, 2026
Merged

mc-nv merged 3 commits into
mainfrom
mchornyi/TRI-1691/before-ngc-release-advance-master-branch-to-next-upstream-release

Conversation

@mc-nv

@mc-nv mc-nv commented Sep 1, 2026 •

Copy link
Copy Markdown
Contributor

What does the PR do?

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:

Where should the reviewer start?

build.py DEFAULT_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, with TRITON_NIGHTLY=1 and TRITON_SBSA=1.

  • Local verification: per-repo pre-commit run --files <changed> passes with no auto-fixes.

  • CI Pipeline ID:

Caveats:

  • Do not merge before the model-repository mount point is rotated: TRITON_SERVER_MODEL_REPO_VERSION derives from TRITON_CONTAINER_VERSION, so 26.09dev must 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)

  • Relates to: TRI-1691

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.
@greptile-apps

greptile-apps Bot commented Sep 1, 2026

Copy link
Copy Markdown

Greptile Summary

The 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.

  • Updates build, SDK, deployment, documentation, and QA defaults to the 26.08 upstream containers.
  • Migrates RHEL builds from a pyenv-installed interpreter to the manylinux Python layout and restores the static embedding library during backend builds.
  • Advances ONNX Runtime, OpenVINO, DCGM, QA model-generation versions, and compatibility documentation.
  • Removes obsolete pre-Python-3.12 backend test setup and corresponding build-preset options.

Confidence Score: 5/5

The 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

Filename Overview
build.py Advances upstream component versions and replaces RHEL pyenv setup with the manylinux Python toolchain and static embedding library.
qa/common/gen_qa_model_repository Aligns generated QA repositories with the 26.09dev server train, 26.08 upstreams, ONNX 1.22.0, and opset 26.
qa/common/gen_qa_model_repository.py Keeps Python model-generation defaults aligned with the shell driver and central build version map.
qa/L0_backend_python/test.sh Removes obsolete alternate-interpreter setup while retaining Python 3.12 validation and default-version environment coverage.
compose.py Updates the DCGM fallback and cleans up regex escaping without changing matching semantics.
tools/build/build_presets.py Removes mapping for the retired RHEL Python-version build option.
deploy/gke-marketplace-app/server-deployer/chart/triton/values.yaml Advances the marketplace image, published version, and sample model repository to the 26.08 release.
docs/introduction/compatibility.md Adds the 26.08 vLLM container and ONNX Runtime compatibility rows.

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
Loading

Reviews (1): Last reviewed commit: "docs: add 26.08 rows to the release comp..." | Re-trigger Greptile

@mc-nv
mc-nv merged commit 0806f17 into main Sep 2, 2026
4 checks passed
@mc-nv
mc-nv deleted the mchornyi/TRI-1691/before-ngc-release-advance-master-branch-to-next-upstream-release branch September 2, 2026 01:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Build Build system or external dependencies (build: PRs) cherry-pick Cherry-picked from another branch chore Maintenance work, no production code change (chore: PRs) Documentation Improvements or additions to documentation (docs: PRs)

Development

Successfully merging this pull request may close these issues.

2 participants