[None][chore] bump version to 1.3.0rc5.post1 - #11788
Conversation
Signed-off-by: Tyler Burt <195370667+tburt-nv@users.noreply.github.com>
|
/bot skip --comment "version bump only" |
📝 WalkthroughWalkthroughVersion bump from 1.3.0rc5 to 1.3.0rc5.post1 across release metadata files. Updates include the release badge in README.md, the tensorrt_llm package constraint in examples/constraints.txt, and the module-level Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Possibly related PRs
Suggested reviewers
🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Tip Try Coding Plans. Let us write the prompt for your AI agent so you can ship faster (with fewer bugs). Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@tensorrt_llm/version.py`:
- Line 15: Update the NVIDIA copyright header in tensorrt_llm/version.py to
include 2026 in the SPDX copyright year range (i.e., extend the existing range
that currently ends at 2025 to include 2026); locate the header near the top of
the file (above the __version__ declaration) and modify the year range
accordingly so the file reflects the latest meaningful modification year.
|
PR_Github #37099 [ skip ] triggered by Bot. Commit: |
|
PR_Github #37099 [ skip ] completed with state |
74f56e8
into
NVIDIA:release/1.3.0rc5.post1
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)
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.Summary by CodeRabbit