docs(server): update README and versions for r26.05#8780
Merged
Conversation
Strip the development suffix from TRITON_VERSION (2.69.0dev -> 2.69.0) and from build.py DEFAULT_TRITON_VERSION_MAP release_version / triton_container_version (26.05dev -> 26.05). upstream_container_version remains 26.04. Remove the main-branch under-development WARNING banner from README.md and bump r26.04 / 26.04 NGC tag references to r26.05 / 26.05 across README, Dockerfile.sdk, deploy charts and schemas, docs, python/openai, and qa model-repo scripts. Update release_notes.md to point to the 26.05 release page. compatibility.md is excluded; it is updated separately as part of the release runbook. Refs TRI-1048
whoisj
approved these changes
May 13, 2026
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
2 participants
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?
Code-freeze release bump for the r26.05 branch. Strips the development suffix from version strings, removes the main-branch "under-development" WARNING banner from README, and bumps r26.04 / 26.04 NGC tag references to r26.05 / 26.05 across docs, deploy charts/schemas, Dockerfile.sdk, and QA model-repo scripts. Mirrors the prior r26.04 release commit
688a5fa9 docs(server): update README and versions for r26.04 (#8729).Checklist
<commit_type>: <Title>Commit Type:
Related PRs:
Where should the reviewer start?
TRITON_VERSIONandbuild.pyDEFAULT_TRITON_VERSION_MAPfor the canonical version source-of-truth.README.mdto confirm the WARNING banner is removed and NGC tags are bumped.docs/introduction/release_notes.mdheader.appVersion/publishedVersion/ image tag fields).Test plan:
Verified
git grep -nE "26\.0[34]|r26\.04|2\.68\.0|under-development"returns no hits outside the excludeddocs/introduction/compatibility.mdand the (intentionally retained)upstream_container_version=26.04andsrc/python/build_wheel.pyillustrative comment.Verified
TRITON_VERSIONis exactly2.69.0(nodev).pre-commit hooks pass locally.
CI Pipeline ID:
Caveats:
server/docs/introduction/compatibility.mdis intentionally excluded; it is updated separately in the release runbook step.upstream_container_versionstays26.04(paired with the agreed release set).DEFAULT_TRITON_VERSION_MAP(ORT, OpenVINO, DCGM, RHEL Python) are not touched here.Background
At code freeze for the 26.05 release the
r26.05branch must stop tracking the under-development banner that only belongs onmain, and version strings must lose thedevsuffix so release-train tags match across server, charts, and docs. See TRI-1048.Related Issues: