chore: upgrade dependencies (canary)

[ParticularlyPythonicBS]

Summary by CodeRabbit

• Chores
  • Updated development and project dependencies: mypy (1.20.0 → 1.20.1) and rich (14.3.4 → 15.0.0).

[coderabbitai]

Walkthrough

Updated dependencies in development and production requirements files: mypy from 1.20.0 to 1.20.1, and rich from 14.3.4 to 15.0.0, with corresponding SHA256 hash updates across both files.

Changes

Cohort / File(s)	Summary
Development Requirements requirements-dev.txt	Updated mypy (1.20.0 → 1.20.1) and rich (14.3.4 → 15.0.0) with new SHA256 hashes.
Production Requirements requirements.txt	Updated rich (14.3.4 → 15.0.0) with new SHA256 hashes.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~4 minutes

Possibly related PRs

• chore: upgrade dependencies (canary) #311: Modifies the same rich dependency in requirements files but targets a different version, indicating parallel dependency management efforts.

🚥 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 'chore: upgrade dependencies (canary)' clearly summarizes the main change—updating development and production dependencies to newer versions with the canary designation indicating testing purposes.
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 unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch unstable

---

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

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

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@requirements.txt`:
- Around line 566-568: The pinned dependency rich==15.0.0 is invalid; change the
requirement to a real released version (e.g., rich==14.3.3) in the
requirements.txt entry that currently lists "rich==15.0.0" and update/remove the
accompanying --hash lines to match the new version (or regenerate the
lockfile/requirements via your dependency tool such as pip-compile/poetry/pip
freeze) so the file contains the correct version and valid hashes.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: f8037f93-b3f3-48d4-87a3-ae227547a605

📥 Commits

Reviewing files that changed from the base of the PR and between 4ec1739 and d3b3db4.

⛔ Files ignored due to path filters (1)

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

📒 Files selected for processing (2)

• requirements-dev.txt
• requirements.txt