Bumping the required version of `rich`

[NellyWhads]

Is your feature request related to a problem? Please describe.
A few key python tools such as python-semantic-release have bumped their minimum version of rich to 14. This renders their newest version incompatible with polylith-cli.

Describe the solution you'd like
Updating the compatible versions of rich to include 14

Describe alternatives you've considered
Not using the modern version of other tools - but this will quickly become limiting.

Additional context
This doesn't consider other packages which also use rich to display in-process progress. They would also most likely impose similar constraints.

[NellyWhads]

@DavidVujic Now that this is merged - when roughly do you plan to cut a new release? I can leave a TODO in my repo to bump this when it's available

[DavidVujic]

A new version is out: (v 1.33.1). Thank you for fixing this!

[NellyWhads]

Haha that was a wicked turn-around time - locked and verified!

[DavidVujic]

Maybe I made a mistake, it looks like Typer (that the Polylith CLI uses) also has a depencency to Rich. I'll investigate!

[NellyWhads]

It looks pretty wide open to me - perhaps it's a version specific issue?

https://github.com/fastapi/typer/blob/55f190efbe85ebd7dd5028f0198441696efa270c/pyproject.toml#L51

[DavidVujic]

Yes, it looks like it should work for sure. When I try, I get rich 13.9. But also, when installing python-semantic-release uv will update the underlying rich to the latest 14 release. So the problem with the non-allowed v14 is at least solved already 😄

[DavidVujic]

After some reading up, there's a difference between how Poetry and uv resolve dependency version. I think that Poetry generally chooses the latest version, but uv the closest lower-bound needed (or something like that).

I'll close this issue, since the original problem is solved. Thank you again for notifying and fixing it!