Skip to content

Bump version to 8.0.7 and update package dependencies#197

Merged
barun-saha merged 1 commit intomainfrom
patch
Jan 31, 2026
Merged

Bump version to 8.0.7 and update package dependencies#197
barun-saha merged 1 commit intomainfrom
patch

Conversation

@barun-saha
Copy link
Owner

@barun-saha barun-saha commented Jan 31, 2026

Summary by CodeRabbit

  • Chores
    • Updated multiple package dependencies to latest versions for improved stability.
    • Revised AI provider integrations.
    • Released version 8.0.7.

✏️ Tip: You can customize this high-level summary in your review settings.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Jan 31, 2026

📝 Walkthrough

Walkthrough

This PR updates project dependencies in requirements.txt and increments the version number. Key changes include upgrading multiple package versions, replacing google-generativeai with google-genai, adding litellm and streamlit, and updating existing packages like pypdf and ollama.

Changes

Cohort / File(s) Summary
Dependency Version Updates
requirements.txt
Updated 10+ package versions including python-dotenv[cli], gitpython, json-repair, idna, pypdf, ollama, and protobuf. Replaced google-generativeai with google-genai. Added litellm, streamlit, lxml, tqdm, numpy, scikit-learn, certifi, urllib3, anyio, and httpx.
Version Bump
src/slidedeckai/_version.py
Incremented __version__ from '8.0.6' to '8.0.7'.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

Poem

🐰 A hop through dependencies, all trimmed and neat!
Version eight-point-seven makes the release complete.
Google-genai now leads the way,
With litellm joining for a brighter day!
Requirements refreshed, our project flies—
hop hop hop toward the skies! 🚀

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately captures both main changes: version bump to 8.0.7 and dependency updates across multiple packages.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing touches
  • 📝 Generate docstrings
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch patch

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

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

@codecov
Copy link

codecov bot commented Jan 31, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

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: 1

🤖 Fix all issues with AI agents
In `@requirements.txt`:
- Around line 11-12: Update requirements.txt to pin the google-genai dependency
to a specific compatible version (e.g., change "google-genai" to
"google-genai~=1.58.0") to ensure reproducible builds, and remove the
commented-out "#google-generativeai" line to reduce clutter.
🧹 Nitpick comments (2)
requirements.txt (2)

26-27: Consider pinning numpy version for compatibility.

numpy is unpinned while scikit-learn~=1.5.1 is pinned. Since scikit-learn depends on specific numpy versions, leaving numpy unpinned could lead to compatibility issues or unexpected behavior.

Suggested fix
-numpy
+numpy~=1.26.4

Or use whatever numpy version is compatible with your scikit-learn and torch requirements.


35-35: Clarify huggingface-hub version intent.

The version specifier #~=0.24.5 is commented out, leaving the package unpinned. If this is intentional (e.g., to allow latest), consider removing the comment entirely. If a specific version is needed, uncomment the specifier.

Suggested options

Option 1 - Pin to a version:

-huggingface-hub  #~=0.24.5
+huggingface-hub~=0.24.5

Option 2 - Remove stale comment:

-huggingface-hub  #~=0.24.5
+huggingface-hub

Comment on lines +11 to +12
#google-generativeai # ~=0.8.3
google-genai
Copy link
Contributor

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟡 Minor

🧩 Analysis chain

🌐 Web query:

google-genai package pypi python

💡 Result:

google-genai is Google’s Gen AI Python SDK on PyPI for calling Gemini Developer API and Vertex AI from Python. [1]

  • Install: pip install google-genai [1]
  • Import: from google import genai and from google.genai import types [1]
  • Create a client:
    • Gemini Developer API: genai.Client(api_key="GEMINI_API_KEY") [1]
    • Vertex AI: genai.Client(vertexai=True, project="...", location="us-central1") [1]
  • Latest release shown on PyPI: 1.58.0 (uploaded Jan 15, 2026). [1]
  • Official downloads page / repo pointer: Google lists google-genai as the Python library and points to googleapis/python-genai. [2]

Sources: PyPI project page for google-genai [1]; Google AI for Developers “Gemini API libraries” downloads page [2].


Pin google-genai to a specific version for reproducibility.

The google-genai package is added without version pinning, which can lead to non-reproducible builds. Pin it to a compatible release specifier like ~=1.58.0 to match the convention used for other dependencies.

Also, remove the commented-out google-generativeai line to reduce clutter.

🤖 Prompt for AI Agents
In `@requirements.txt` around lines 11 - 12, Update requirements.txt to pin the
google-genai dependency to a specific compatible version (e.g., change
"google-genai" to "google-genai~=1.58.0") to ensure reproducible builds, and
remove the commented-out "#google-generativeai" line to reduce clutter.

@barun-saha barun-saha merged commit d862acb into main Jan 31, 2026
9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant