Skip to content

Conversation

@nv-anants
Copy link
Contributor

@nv-anants nv-anants commented May 28, 2025

Overview:

  • update dynamo versions for 0.3.0 release
  • update nixl to latest 0.3.0 rc build

Summary by CodeRabbit

  • Chores
    • Updated version numbers across multiple packages and dependencies to 0.3.0.
    • Updated the patched vLLM Python package version to 0.8.4.post2 in the Docker build.
    • Updated the NIXL commit used in the build process.
  • Documentation
    • Revised the support matrix to reflect the new package and dependency versions.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented May 29, 2025

Walkthrough

This update synchronizes version numbers across multiple project components, including Rust and Python packages, Docker build scripts, and documentation. It increments versions for internal dependencies, patched external packages, and updates references in documentation and build scripts to ensure consistency with the new release.

Changes

Files/Paths Change Summary
Cargo.toml, lib/runtime/examples/Cargo.toml Updated workspace and example package versions from 0.2.1 to 0.3.0; updated local dependency versions.
lib/bindings/python/Cargo.toml, pyproject.toml Bumped Python binding and project versions from 0.2.1 to 0.3.0; updated ai-dynamo-runtime dependency.
lib/llm/Cargo.toml Updated optional dependency nixl-sys from 0.2.1-rc.3 to 0.3.0-rc.2.
container/Dockerfile.vllm Changed patched vLLM Python package version from 0.8.4.post1 to 0.8.4.post2.
container/build.sh Updated NIXL_COMMIT hash to a new commit for build consistency.
docs/support_matrix.md Updated package, dependency, and patch version numbers in support matrix documentation.

Suggested reviewers

  • oandreeva-nv
  • ptarasiewiczNV
  • ishandhanani

Poem

Version numbers hop and leap,
Like rabbits bounding, never asleep.
From 0.2.1 to 0.3.0 we go,
Docker and docs now in the flow.
With hashes and patches all aligned,
The garden of code is neatly defined!
🐇✨


📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 11fb13e and 66a0c0e.

📒 Files selected for processing (1)
  • container/Dockerfile.vllm (1 hunks)
✅ Files skipped from review due to trivial changes (1)
  • container/Dockerfile.vllm
⏰ Context from checks skipped due to timeout of 90000ms (5)
  • GitHub Check: Build Documentation
  • GitHub Check: Build and Test - vllm
  • GitHub Check: pre-merge-rust (.)
  • GitHub Check: pre-merge-rust (lib/runtime/examples)
  • GitHub Check: pre-merge-rust (lib/bindings/python)

🪧 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 (1)
docs/support_matrix.md (1)

63-76: Surround tables with blank lines
To satisfy Markdown lint rule MD058 and improve readability, please add an empty line immediately before and after each table (both the Runtime Dependency and Build Dependency tables).

🧰 Tools
🪛 markdownlint-cli2 (0.17.2)

63-63: Tables should be surrounded by blank lines
null

(MD058, blanks-around-tables)


71-71: Tables should be surrounded by blank lines
null

(MD058, blanks-around-tables)

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 93ca9df and 51424f1.

⛔ 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 (8)
  • Cargo.toml (2 hunks)
  • container/Dockerfile.vllm (1 hunks)
  • container/build.sh (1 hunks)
  • docs/support_matrix.md (1 hunks)
  • lib/bindings/python/Cargo.toml (2 hunks)
  • lib/llm/Cargo.toml (1 hunks)
  • lib/runtime/examples/Cargo.toml (1 hunks)
  • pyproject.toml (2 hunks)
🧰 Additional context used
🪛 markdownlint-cli2 (0.17.2)
docs/support_matrix.md

71-71: Tables should be surrounded by blank lines
null

(MD058, blanks-around-tables)

⏰ Context from checks skipped due to timeout of 90000ms (5)
  • GitHub Check: Build and Test - vllm
  • GitHub Check: Build Documentation
  • GitHub Check: pre-merge-rust (lib/runtime/examples)
  • GitHub Check: pre-merge-rust (lib/bindings/python)
  • GitHub Check: pre-merge-rust (.)
🔇 Additional comments (12)
lib/runtime/examples/Cargo.toml (1)

24-24: Example workspace version bumped to 0.3.0.
This update aligns the example manifest with the root workspace version.

lib/llm/Cargo.toml (1)

84-84:

❓ Verification inconclusive

Ensure Nixl-sys version aligns with build and docs.
The optional dependency nixl-sys has been updated to 0.3.0-rc.2. Please verify that the NIXL_COMMIT in container/build.sh and the reference in docs/support_matrix.md are also updated to match this release candidate.


🏁 Script executed:

#!/bin/bash
# Verify nixl-sys version consistency
rg -n 'nixl-sys' --glob '*.toml'
rg -n 'NIXL_COMMIT' container/build.sh
rg -n 'nixl-sys' docs/support_matrix.md

Length of output: 667


Ensure Nixl-sys version alignment in build and docs
The Cargo.toml entry has been bumped to 0.3.0-rc.2, but:

  • container/build.sh (around line 112): NIXL_COMMIT is still set to f531404be4866d85ed618b3baf4008c636798d63. Please confirm this hash actually points at the 0.3.0-rc.2 release tag (or update it to the correct commit).
  • docs/support_matrix.md: no nixl-sys entry was found. If the support matrix needs to reflect the new optional dependency, please add or update it accordingly.
pyproject.toml (2)

18-18: Project version bumped to 0.3.0.
The version field has been updated in line with the coordinated release.


32-32: Runtime dependency updated to 0.3.0.
The ai-dynamo-runtime dependency version now matches the project version bump.

Cargo.toml (2)

42-44: Path dependencies version-aligned.
The dynamo-runtime, dynamo-llm, and dynamo-tokens path dependencies are correctly set to version 0.3.0.


31-31:

✅ Verification successful

Workspace package version bumped to 0.3.0.
This aligns the root manifest with related component versions.


🏁 Script executed:

#!/bin/bash
# Check for any remaining "0.2.1" references in TOML manifests
rg -n 'version = "0.2.1"' --glob '*.toml'

Length of output: 43


Workspace package version updated to 0.3.0 – no remaining references to 0.2.1
All Cargo.toml manifests now use version 0.3.0; a ripgrep search returned zero hits for version = "0.2.1". ✔️

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

22-22: Python binding version updated to 0.3.0.
The package dynamo-py3 version was bumped to match the workspace release.

container/build.sh (1)

112-112:

❓ Verification inconclusive

Validate updated NIXL commit hash
The NIXL_COMMIT was bumped to f531404be4866d85ed618b3baf4008c636798d63 for the 0.3.0 release. Please verify that this hash actually exists on the ai-dynamo/nixl main branch and corresponds to the intended tag.

Run this to confirm:


🏁 Script executed:

git ls-remote https://github.com/ai-dynamo/nixl.git f531404be4866d85ed618b3baf4008c636798d63

Length of output: 94


Confirm NIXL_COMMIT hash
The commit f531404be4866d85ed618b3baf4008c636798d63 was not found in the ai-dynamo/nixl remote. Please verify that this hash exists on the main branch and corresponds to the intended 0.3.0 tag.

Locations to check:

  • container/build.sh: line 112 (NIXL_COMMIT=f531404be4866d85ed618b3baf4008c636798d63)
container/Dockerfile.vllm (1)

172-172: Bump patched vLLM package version
The VLLM_PATCHED_PACKAGE_VERSION has been updated from 0.8.4.post1 to 0.8.4.post2, matching the new patched release. Ensure that any downstream metadata (wheel filenames, dist-info directories, etc.) and the support matrix are consistent with this change.

docs/support_matrix.md (3)

65-68: Update runtime dependency versions
The runtime table entries for ai-dynamo, ai-dynamo-runtime, ai-dynamo-vllm, and NIXL have been correctly bumped to 0.3.0 and 0.8.4.post2 respectively to align with the new release.


74-76: Update build dependency table
The build dependency versions for ai-dynamo-vllm and NIXL were updated to 0.8.4.post2 and 0.3.0 as expected.


79-79: Confirm explanatory note
The note stating *ai-dynamo-vllm v0.8.4.post2 is a customized patch of v0.8.4 from vLLM accurately describes the patched package version.

@nv-anants nv-anants enabled auto-merge (squash) May 29, 2025 17:13
@nv-anants nv-anants merged commit 9d9a1d9 into main May 29, 2025
15 of 22 checks passed
@nv-anants nv-anants deleted the anants/update-versions-0.3.0 branch May 29, 2025 17:30
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