Skip to content

Conversation

@nv-anants
Copy link
Contributor

@nv-anants nv-anants commented Jul 7, 2025

Overview:

Update versions for 0.3.2 release

Summary by CodeRabbit

  • Chores
    • Updated version numbers for core packages and dependencies from 0.3.1 to 0.3.2.
    • Updated patched vLLM package version from 0.8.4.post3 to 0.8.4.post4.
    • Refreshed documentation to reflect new package and dependency versions.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Jul 7, 2025

Walkthrough

This update increments version numbers across multiple project files, including Rust and Python package manifests, Docker build arguments, and documentation, moving from version 0.3.1 to 0.3.2 for several components. The vLLM patched package version is also updated from 0.8.4.post3 to 0.8.4.post4 in both the Dockerfile and documentation.

Changes

Files/Paths Change Summary
Cargo.toml, lib/bindings/python/Cargo.toml, lib/runtime/examples/Cargo.toml Bumped workspace and package versions from 0.3.1 to 0.3.2
pyproject.toml Updated ai-dynamo and ai-dynamo-runtime versions to 0.3.2
container/Dockerfile.vllm Changed VLLM_PATCHED_PACKAGE_VERSION from 0.8.4.post3 to 0.8.4.post4
docs/support_matrix.md Updated ai-dynamo, ai-dynamo-runtime, ai-dynamo-vllm, and build dependency versions in documentation

Possibly related PRs

Poem

A hop, a skip, a version jump—
From one point three one to two we bump!
Docker and docs, all in line,
vLLM patched, now looking fine.
The codebase grows, the numbers climb,
This bunny’s proud of version time! 🐇✨


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (2)
docs/support_matrix.md (2)

83-85: Footnote marker is embedded in the version string—may confuse copy-paste or tooling

1.0.0rc² places the superscript marker inside the semver token. Consider moving the marker outside the version text to avoid users copying an invalid string (e.g. 1.0.0rc2 ²).

-| **TensorRT-LLM**     | 1.0.0rc²                                                                        |
+| **TensorRT-LLM**     | 1.0.0rc2²                                                                       |

88-90: Footnote text refers to “TensorRT-LLM” versions—keep wording generic

Current wording implies versions may “change”; consider clarifying that supported versions are documented in this matrix and image build files, not an open-ended promise.

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 1630f8b and 979ea7b.

⛔ Files ignored due to path filters (3)
  • Cargo.lock is excluded by !**/*.lock
  • lib/bindings/python/Cargo.lock is excluded by !**/*.lock
  • lib/runtime/examples/Cargo.lock is excluded by !**/*.lock
📒 Files selected for processing (6)
  • Cargo.toml (2 hunks)
  • container/Dockerfile.vllm (1 hunks)
  • docs/support_matrix.md (1 hunks)
  • lib/bindings/python/Cargo.toml (1 hunks)
  • lib/runtime/examples/Cargo.toml (1 hunks)
  • pyproject.toml (2 hunks)
🧰 Additional context used
🧠 Learnings (4)
lib/bindings/python/Cargo.toml (1)
Learnt from: biswapanda
PR: ai-dynamo/dynamo#1412
File: lib/bindings/python/src/dynamo/runtime/logging.py:100-100
Timestamp: 2025-06-06T21:48:35.214Z
Learning: In the Dynamo codebase, BentoML has been completely removed from all executable code, with only documentation and attribution references remaining. The error_loggers configuration in lib/bindings/python/src/dynamo/runtime/logging.py should not include "bentoml" since those modules no longer exist.
Cargo.toml (2)
Learnt from: nnshah1
PR: ai-dynamo/dynamo#1444
File: tests/fault_tolerance/utils/metrics.py:30-32
Timestamp: 2025-07-01T13:55:03.940Z
Learning: The `@dynamo_worker()` decorator in the dynamo codebase returns a wrapper that automatically injects the `runtime` parameter before calling the wrapped function. This means callers only need to provide the non-runtime parameters, while the decorator handles injecting the runtime argument automatically. For example, a function with signature `async def get_metrics(runtime, log_dir)` decorated with `@dynamo_worker()` can be called as `get_metrics(log_dir)` because the decorator wrapper injects the runtime parameter.
Learnt from: kthui
PR: ai-dynamo/dynamo#1424
File: lib/runtime/src/pipeline/network/egress/push_router.rs:204-209
Timestamp: 2025-06-13T22:07:24.843Z
Learning: The codebase uses async-nats version 0.40, not the older nats crate. Error handling should use async_nats::error::Error variants, not nats::Error variants.
pyproject.toml (1)
Learnt from: biswapanda
PR: ai-dynamo/dynamo#1412
File: lib/bindings/python/src/dynamo/runtime/logging.py:100-100
Timestamp: 2025-06-06T21:48:35.214Z
Learning: In the Dynamo codebase, BentoML has been completely removed from all executable code, with only documentation and attribution references remaining. The error_loggers configuration in lib/bindings/python/src/dynamo/runtime/logging.py should not include "bentoml" since those modules no longer exist.
docs/support_matrix.md (1)
Learnt from: biswapanda
PR: ai-dynamo/dynamo#1412
File: lib/bindings/python/src/dynamo/runtime/logging.py:100-100
Timestamp: 2025-06-06T21:48:35.214Z
Learning: In the Dynamo codebase, BentoML has been completely removed from all executable code, with only documentation and attribution references remaining. The error_loggers configuration in lib/bindings/python/src/dynamo/runtime/logging.py should not include "bentoml" since those modules no longer exist.
🔇 Additional comments (6)
container/Dockerfile.vllm (1)

165-167: Version bump looks consistent – double-check wheel re-pack logic

The new VLLM_PATCHED_PACKAGE_VERSION="0.8.4.post4" is consumed a few lines below when the mv/sed commands rename the dist-info directory and update metadata. If a .post4 wheel is not yet published (or internally available) those commands will fail at build time.

Please trigger a quick CI build or locally build the image to ensure the wheel is found and the dist-info patching succeeds.

lib/bindings/python/Cargo.toml (1)

20-23: Crate version bump acknowledged

dynamo-py3 now tracks the workspace’s 0.3.2 release. No other metadata touched — LGTM.

lib/runtime/examples/Cargo.toml (1)

23-25: Example workspace version updated

The examples crate now points to 0.3.2, keeping the whole workspace in sync. Looks good.

pyproject.toml (1)

18-19: Python package & runtime dependency bumped – verify publish order

ai-dynamo and its hard-pinned dependency ai-dynamo-runtime==0.3.2 were both incremented. Ensure the runtime wheel is published to the same index before this package to avoid install failures in fresh environments.

Also applies to: 31-32

Cargo.toml (1)

30-45: Workspace and local crate versions aligned

Root workspace version and the three internal crates have been bumped to 0.3.2. Consistency across all manifests confirmed.

docs/support_matrix.md (1)

73-75: Version bump looks correct, but verify other docs stay in sync

ai-dynamo* packages are now listed as 0.3.2. Double-check that every place that shows an install command (README, Quick-Start, container build instructions, etc.) also references 0.3.2 so users don’t get mismatched guidance.

@nv-anants nv-anants merged commit c4935b3 into main Jul 7, 2025
17 of 18 checks passed
@nv-anants nv-anants deleted the anants/versions-032 branch July 7, 2025 21:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants