[None][chore] Bump version to 1.3.0rc18

[yuanjingx87]

Summary by CodeRabbit

• Chores
  • Release candidate version updated to 1.3.0rc18 across all package documentation and dependency constraints.

Description

Test Coverage

PR Checklist

Please review the following before submitting your PR:

• PR description clearly explains what and why. If using CodeRabbit's summary, please make sure it makes sense.

• PR Follows TRT-LLM CODING GUIDELINES to the best of your knowledge.

• Test cases are provided for new code paths (see test instructions)

• If PR introduces API changes, an appropriate PR label is added - either api-compatible or api-breaking. For api-breaking, include BREAKING in the PR title.

• Any new dependencies have been scanned for license and vulnerabilities

• CODEOWNERS updated if ownership changes

• Documentation updated as needed

• Update tava architecture diagram if there is a significant design change in PR.

• The reviewers assigned automatically/manually are appropriate for the PR.

• Please check this after reviewing the above items as appropriate for this PR.

GitHub Bot Help

To see a list of available CI bot commands, please comment /bot help.

[yuanjingx87]

/bot skip --comment "Version bumping, no need to run CI"

[coderabbitai]

📝 Walkthrough

Walkthrough

This PR updates the TensorRT-LLM version number from 1.3.0rc17 to 1.3.0rc18 across three files: the package version module, the README release badge, and the pinned dependency in the examples constraints file.

Changes

Release Candidate Version 1.3.0rc18

Layer / File(s)	Summary
Release candidate version 1.3.0rc18 tensorrt_llm/version.py, README.md, examples/constraints.txt	The __version__ constant is bumped to 1.3.0rc18, and the README release badge and example constraints dependency are synchronized to match.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• NVIDIA/TensorRT-LLM#12511: Both PRs perform a version bump by updating tensorrt_llm/version.py's __version__ and synchronizing the README release badge and examples/constraints.txt pinned tensorrt_llm version to the next rc number.
• NVIDIA/TensorRT-LLM#11864: Both PRs perform the same kind of version bump across README.md, examples/constraints.txt, and tensorrt_llm/version.py (rc17→rc18 vs rc6→rc7), changing the same version declarations/badges.
• NVIDIA/TensorRT-LLM#11688: Both PRs are simple version bumps, updating the same version strings in README.md, examples/constraints.txt, and tensorrt_llm/version.py (rc5→rc6 vs rc17→rc18).

Suggested reviewers

• venkywonka
• nv-guomingz
• chang-l

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The PR description contains only the template boilerplate with no actual description, test coverage details, or explanation of the version bump.	Add a brief description explaining why the version is being bumped to 1.3.0rc18, and list any relevant tests or validation performed for this release.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and concisely describes the main change: bumping the version from 1.3.0rc17 to 1.3.0rc18 across README, constraints, and version files.
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 docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch preview/bump/main

---

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

[coderabbitai]

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

tensorrt_llm/version.py (1)

1-1: ⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

Update the NVIDIA copyright year on this modified Python file.

This file was changed in 2026, but the header still ends at 2025. Please update the header year range accordingly.

As per coding guidelines: "NVIDIA copyright header on ALL new files (update year on modified files)".

Also applies to: 15-15

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@tensorrt_llm/version.py` at line 1, Update the SPDX header year range from
"2022-2025" to include 2026 (i.e., "2022-2026") for the modified file; find the
existing header comment line(s) that contain "SPDX-FileCopyrightText: Copyright
(c) 2022-2025 NVIDIA CORPORATION & AFFILIATES" and change the end year to 2026
so the header reflects the 2026 modification.

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Outside diff comments:
In `@tensorrt_llm/version.py`:
- Line 1: Update the SPDX header year range from "2022-2025" to include 2026
(i.e., "2022-2026") for the modified file; find the existing header comment
line(s) that contain "SPDX-FileCopyrightText: Copyright (c) 2022-2025 NVIDIA
CORPORATION & AFFILIATES" and change the end year to 2026 so the header reflects
the 2026 modification.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: 5f3d43b9-9aa2-4cb8-8082-cc1d0c184af6

📥 Commits

Reviewing files that changed from the base of the PR and between cd38dfb and 6f04666.

📒 Files selected for processing (3)

• README.md
• examples/constraints.txt
• tensorrt_llm/version.py

[tensorrt-cicd]

PR_Github #51666 [ skip ] triggered by Bot. Commit: 6f04666 Link to invocation

[tensorrt-cicd]

PR_Github #51666 [ skip ] completed with state SUCCESS. Commit: 6f04666
Skipping testing for commit 6f04666

Link to invocation