chore(deps): bump the pip group across 2 directories with 2 updates

[thomascolden585-svg]

Feature Description

Summary

This issue tracks a dependency maintenance update for the Python dependency group managed in this monorepo.
The goal is to keep package versions current and reduce risk from outdated transitive dependencies, while preserving compatibility with existing integrations.

Scope

• Apply the pip dependency group bump across 2 target directories.
• Include 2 package updates from the current dependency update batch.
• Keep all changes limited to dependency/version metadata unless a compatibility fix is strictly required.

Reason

Why This Matters

• Maintains healthy dependency posture across actively maintained packages.
• Aligns with the repository's automated dependency strategy (uv + grouped updates).
• Reduces CI instability and future upgrade friction by handling small updates continuously.

Value of Feature

Implementation Notes

• Follow the repository contribution flow in CONTRIBUTING.md.
• Use uv workflows for dependency synchronization and validation.
• If any package versions are changed in package-level pyproject.toml files, apply required version bump conventions.

Validation Checklist

• Dependency updates are scoped to the intended 2 directories only.
• Local lint passes (uv run make lint).
• Relevant tests pass in each modified package (uv run -- pytest).
• No unrelated refactors or feature changes are included.
• Changelog/release automation remains unaffected.

Definition of Done

• PR is opened with title: chore(deps): bump the pip group across 2 directories with 2 updates
• CI passes on the dependency update PR.
• Review confirms no runtime or API regressions.

[enjoyandlove]

Thanks for outlining this dependency update clearly.

The scoped approach—limiting changes to the defined directories and keeping updates focused on version metadata—is a good way to reduce risk while maintaining a healthy dependency posture. Aligning with the existing uv-based workflow and grouped update strategy should also help keep CI stable and avoid larger, more disruptive upgrades later.

The validation checklist is well defined and covers the key areas (linting, tests, and scope control). As long as any required compatibility fixes remain minimal and isolated, this should be a safe and valuable maintenance update.

Overall, this looks like a solid, low-risk improvement to keep dependencies current and manageable.

[dosubot]

Hi, @thomascolden585-svg. I'm Dosu, and I'm helping the LlamaIndex team manage their backlog and am marking this issue as stale.

Issue Summary

• You opened this as a scoped dependency maintenance task to bump the Python pip group across two directories.
• The intended change was limited to version metadata for two packages, following the repo’s uv-based workflow.
• The goal was to keep the update low-risk and avoid unrelated refactors or runtime/API changes.
• In the only comment so far, @enjoyandlove agreed that the tightly bounded approach should help keep CI stable.

Next Steps

• If this is still relevant on the latest version of the LlamaIndex repository, please comment here to keep the discussion open.
• Otherwise, this issue will be automatically closed in 7 days.

Thanks for your understanding and contribution!