Skip to content

[None][docs] Add deprecation notice to legacy support-matrix.md#14495

Open
fuergaosi233 wants to merge 1 commit into
NVIDIA:mainfrom
fuergaosi233:fix/legacy-support-matrix-deprecation-notice
Open

[None][docs] Add deprecation notice to legacy support-matrix.md#14495
fuergaosi233 wants to merge 1 commit into
NVIDIA:mainfrom
fuergaosi233:fix/legacy-support-matrix-deprecation-notice

Conversation

@fuergaosi233
Copy link
Copy Markdown

@fuergaosi233 fuergaosi233 commented May 23, 2026

Background

docs/source/legacy/reference/support-matrix.md is a legacy page that is still publicly accessible and indexed, but it lacks any indication that it is outdated. Users landing on this page may act on stale information — for example, the page is missing 15+ architectures that are present in the current docs/source/models/supported-models.md.

Compared with the current supported-models page, the legacy support-matrix is missing entries like: Llama 4, Qwen 3, Gemma 3, Phi 4, DeepSeek-R1, EXAONE 4.0, and many others.

Changes

Added a {deprecated} admonition at the top of the page, pointing users to the up-to-date docs/source/models/supported-models.md page:

\`\`\`{deprecated}
This page is outdated and no longer maintained. Please refer to the up-to-date [Supported Models](../../models/supported-models.md) page instead.
\`\`\`

This follows the Sphinx {deprecated} directive convention and renders visibly in the built documentation without removing or altering any existing content on the page.

Verification

Confirmed the legacy page has no deprecation notice:

$ head -5 docs/source/legacy/reference/support-matrix.md
# Support Matrix
TensorRT-LLM optimizes the performance of a range of well-known models...

Confirmed the current page exists at the linked path:

$ ls docs/source/models/supported-models.md
docs/source/models/supported-models.md

Summary by CodeRabbit

  • Documentation
    • Marked the legacy support matrix documentation as deprecated, with a notice directing users to the updated "Supported Models" reference page.

Review Change Stack

Signed-off-by: holegots <fuergaosi@gmail.com>
@fuergaosi233 fuergaosi233 requested a review from a team as a code owner May 23, 2026 19:34
@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented May 23, 2026

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: 3c1cac4c-3f71-43dc-bcf3-f7143c0c4e8e

📥 Commits

Reviewing files that changed from the base of the PR and between c5b0372 and ab60e5e.

📒 Files selected for processing (1)
  • docs/source/legacy/reference/support-matrix.md

📝 Walkthrough

Walkthrough

A Sphinx {deprecated} admonition is added to the top of the legacy support-matrix.md documentation page, indicating the page is outdated and no longer maintained, with a reference to the current Supported Models documentation.

Changes

Documentation Deprecation

Layer / File(s) Summary
Deprecation notice for legacy support matrix
docs/source/legacy/reference/support-matrix.md
A Sphinx {deprecated} admonition is added to the top of the page indicating the page is outdated and directing readers to the current "Supported Models" reference.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly and specifically describes the main change: adding a deprecation notice to the legacy support-matrix documentation file.
Description check ✅ Passed The description is comprehensive, covering background, specific changes made, and verification steps. However, it lacks a Test Coverage section and does not explicitly address PR checklist items as required by the template.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Comment @coderabbitai help to get the list of available commands and usage tips.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant