Chore: Bump versions of twine and rich

[angelofenoglio]

What?

• Bump twine and rich versions

Why?

• Allow python 3.13 release

Summary by CodeRabbit

• Chores
  • Updated dependencies to improve stability and compatibility.
  • Upgraded Rich from 10.4.0 to 14.1.0, bringing enhanced terminal rendering and performance.
  • Upgraded Twine from 3.4.1 to 6.1.0 to align with current packaging tooling.
  • No user-facing behavior changes; functionality remains the same.
  • Improves reliability of packaging and release workflows.

[coderabbitai]

Walkthrough

Updated dependency versions in pyproject.toml: rich from 10.4.0 to 14.1.0 and twine from 3.4.1 to 6.1.0. No code changes.

Changes

Cohort / File(s)	Summary of changes
Dependency upgrades pyproject.toml	Bumped rich (10.4.0 → 14.1.0) and twine (3.4.1 → 6.1.0) in Poetry configuration; no other modifications.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Suggested labels

minor

Suggested reviewers

• Franr
• exequielrafaela
• diego-ojeda-binbash

Poem

Thump-thump goes my fluffy heart with glee,
Two versions hopped ahead—swift as can be.
Richer logs, twine spun tight,
Packaging burrow prepped just right.
Nose twitch, ears perk—ship by night! 🐇✨

Tip

🔌 Remote MCP (Model Context Protocol) integration is now available!

Pro plan users can now connect to remote MCP servers from the Integrations page. Connect with popular remote MCPs such as Notion and Linear to add more context to your reviews and chats.

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 6c42358 and 4d52dbb.

⛔ Files ignored due to path filters (1)

• poetry.lock is excluded by !**/*.lock

📒 Files selected for processing (1)

• pyproject.toml (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: integration_tests_cli_refarch (3.9, 1.3.5-0.2.3)

🔇 Additional comments (2)

pyproject.toml (2)

42-42: Approve Rich 14.1.0 bump – I scanned all Rich imports and call sites (leverage/leverage.py, leverage/logger.py, tests/test_logger.py) and confirmed we only use rich.print, rich.console, and rich.logging.RichHandler. No renamed or removed APIs were detected, and the package metadata declares requires_python = ">=3.8.0", so Python 3.13 compatibility is satisfied.

---

50-50: Twine 6.1.0 upgrade verified: CI publish flags & auth are correct

• Makefile targets
  • make check invokes poetry run twine check dist/* and
  • make push-ci invokes poetry run twine upload --non-interactive --repository-url https://upload.pypi.org/legacy/ dist/*
    ensuring both “check” and “upload” steps are present with no deprecated flags.
• GitHub Actions workflows
  • Steps named “upload” in both release-pypi-build-push-package.yml and release-pypi-build-push-test-package.yml call make push-ci
  • Environment variables set as TWINE_USERNAME=__token__ and TWINE_PASSWORD=${{ secrets.PYPI_TOKEN }}, confirming token-based auth.
• Project requires Python ~3.9–3.13, which satisfies Twine 6.1.0’s requires_python >=3.8.

Optional follow-up: consider migrating to pypa/gh-action-pypi-publish for a more streamlined GitHub Actions integration.

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch Fix/versions-bump

---

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.
  • 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.
• 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 the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

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

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

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.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• 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.

[coveralls]

Pull Request Test Coverage Report for Build 17242237591

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 61.145%

---

Totals
Change from base Build 17228394096:	0.0%
Covered Lines:	2610
Relevant Lines:	4136

---

💛 - Coveralls