Repository navigation
chore(doc,versions): Update README and Versions for 26.11 - #179
Merged
Merged
Conversation
Co-Authored-By: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
Contributor
Author
|
I'll fix CI failures and address comments from users with write access. I'll skip comments containing "(aside)".
|
[Medium impact] The PR appears safe to merge; no actionable issues introduced by these version updates were found. SummaryUpdates Triton server, SDK, and vLLM image references from 26.10 to 26.11 across 17 files.
Reviews (1) · Last reviewed commit: "chore(doc,versions): Update README and V..." · Reviewed by Greptile |
This was referenced Nov 4, 2026
Merged
devin-ai-integration
Bot
requested review from
Vinya567,
mc-nv,
whoisj and
yinggeh
November 4, 2026 00:32
Vinya567
approved these changes
Nov 4, 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
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?
-py3,-py3-sdk,-vllm-python-py3) andBASE_IMAGE_TAG*→ 26.11r26.10image tags andr26.10links →r26.11Checklist
<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?
Any changed
Dockerfile/BASE_IMAGE_TAG*fileTest plan:
Version/doc strings only; pre-commit passes.
Caveats:
TRT-LLM images stay pinned at
26.07-trtllm-python-py3, as in #176.Background
26.11 release-branch bump; same pattern as #176 (26.10).
Related Issues: (use one of the action keywords Closes / Fixes / Resolves / Relates to)