chore: update dynamo and nixl versions for 0.3.1

[nv-anants]

Overview:

update dynamo and nixl versions for 0.3.1
closes: OPS-226

Summary by CodeRabbit

• Chores
  • Updated version numbers for core packages and dependencies to 0.3.1.
  • Incremented patched vLLM package version to 0.8.4.post3.
  • Updated NIXL build commit reference.
• Documentation
  • Refreshed support matrix to reflect new package and dependency versions, and added a note about glibc compatibility with Python 3.12.

[coderabbitai]

Walkthrough

This update increments the version numbers of core packages, dependencies, and documentation references from 0.3.0 to 0.3.1 across the project. It also updates the patched vLLM package version in the Dockerfile, the NIXL commit hash in the build script, and adjusts related documentation to reflect these changes.

Changes

Files / Grouped Paths	Change Summary
Cargo.toml, lib/bindings/python/Cargo.toml, lib/runtime/examples/Cargo.toml	Incremented package versions from 0.3.0 to 0.3.1.
pyproject.toml	Updated project and dependency version from 0.3.0 to 0.3.1.
container/Dockerfile.vllm	Updated vLLM patched package version from 0.8.4.post2 to 0.8.4.post3.
container/build.sh	Changed NIXL commit hash to a newer value.
docs/support_matrix.md	Updated all relevant dependency and build tool versions; added a note for glibc and Python 3.12.

Possibly related PRs

• chore: update dynamo and nixl versions for 0.3.0 #1240: Previous PR updating versions from 0.2.1 to 0.3.0, involving the same files and version metadata, indicating a sequential version bump pattern.

Poem

Version numbers hop ahead,
From zero-three-oh to one instead.
Docker builds and docs align,
With hashes, wheels, and notes so fine.
A patch, a bump, a matrix bright—
The codebase leaps to greater height!
🐇✨

---

📜 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 c232339 and ad02340.

⛔ Files ignored due to path filters (2)

• Cargo.lock is excluded by !**/*.lock
• lib/bindings/python/Cargo.lock is excluded by !**/*.lock

📒 Files selected for processing (1)

• docs/support_matrix.md (1 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• docs/support_matrix.md

⏰ Context from checks skipped due to timeout of 90000ms (4)

• GitHub Check: pre-merge-rust (lib/bindings/python)
• GitHub Check: pre-merge-rust (lib/runtime/examples)
• GitHub Check: Build and Test - vllm
• GitHub Check: pre-merge-rust (.)

---

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

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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.