Rollback rich to >=13.0.0

[PaulCavill]

Breaking change

Proposed change

Dependency downgrade to support Home Assistant

Type of change

• Dependency upgrade
• Bugfix (non-breaking change which fixes an issue)
• New service (thank you!)
• New feature (which adds functionality to an existing service)
• Breaking change (fix/feature causing existing functionality to break)
• Code quality improvements to existing code or addition of tests
• Documentation or code sample

Example of code:

Additional information

• This PR fixes or closes issue: fixes #
• This PR is related to issue:

Checklist

• The code change is tested and works locally.
• Local tests pass. Your PR cannot be merged unless tests pass
• There is no commented out code in this PR.
• Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

• Documentation added/updated to README

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 5a520460-423b-4524-a83d-f82bd0cdd402

📥 Commits

Reviewing files that changed from the base of the PR and between a2998f3 and b90fd94.

📒 Files selected for processing (1)

• requirements.txt

---

📝 Walkthrough

Summary by CodeRabbit

Chores

• Updated internal dependency version constraints to support a broader range of compatible package versions, improving flexibility in deployment environments.

Walkthrough

The requirements.txt dependency constraint for the rich package is relaxed from >=15.0.0 to >=13.0.0, broadening compatibility with earlier compatible versions whilst maintaining a minimum usable version.

Changes

Dependency Update

Layer / File(s)	Summary
Rich minimum version constraint requirements.txt	The rich package minimum version requirement is lowered from >=15.0.0 to >=13.0.0.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 A little constraint, now relaxed with care,
Rich grows more flexible everywhere,
From fifteen down to thirteen true,
Broader paths for all to brew. ✨

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and specifically describes the main change: rolling back the rich dependency version to >=13.0.0, which matches the changeset exactly.
Description check	✅ Passed	The description is related to the changeset, stating 'Dependency downgrade to support Home Assistant', which aligns with the actual dependency version change made in requirements.txt.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

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

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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

[PaulCavill]

@timlaing how long has rich been apart of the requirements? Looks to be add with typer, and that was moved to the CLI install, can we move rich over to?

[timlaing]

IIRC: rich was introduced by the notes support to allow the exporting. Happy for the move to the CLI