Chore(deps): Update rich requirement from ==13.9.* to >=13.9,<14.3#409
Chore(deps): Update rich requirement from ==13.9.* to >=13.9,<14.3#409dependabot[bot] wants to merge 1 commit into
Conversation
Updates the requirements on [rich](https://github.com/Textualize/rich) to permit the latest version. - [Release notes](https://github.com/Textualize/rich/releases) - [Changelog](https://github.com/Textualize/rich/blob/master/CHANGELOG.md) - [Commits](Textualize/rich@v13.9.0...v14.2.0) --- updated-dependencies: - dependency-name: rich dependency-version: 14.2.0 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
|
Failed to retrieve llama text: Invalid URL '/completion': No scheme supplied. Perhaps you meant https:///completion? |
foxpatch-aleph
left a comment
There was a problem hiding this comment.
This is a straightforward dependency relaxation from a pinned ==13.9.* to a range >=13.9,<14.3. The change is safe and correct in isolation — it follows best practices by using a range instead of a strict pin. However, the project also pins textual==0.73, which almost certainly constrains rich to <14.0 in its own metadata. This means the effective resolved version of rich will still be capped at 13.x by the textual constraint, making the <14.3 upper bound unreachable in practice without a corresponding textual upgrade. The PR is not harmful, but it may create a misleading impression about rich 14.x compatibility.
pyproject.toml (line 42): The new upper bound <14.3 is unlikely to be reachable in practice: textual==0.73 (line 45) carries its own transitive constraint on rich<14.0. As a result, pip will still resolve to rich 13.9.x regardless of this change. If the goal is to actually support rich 14.x, textual should be upgraded to a version that itself supports rich 14. If the intent is simply to stop pinning to an exact patch range, >=13.9,<14 would be a more honest bound that reflects the real ceiling imposed by the textual pin.
Updates the requirements on rich to permit the latest version.
Release notes
Sourced from rich's releases.
Changelog
Sourced from rich's changelog.
... (truncated)
Commits
494f83cchangelogd476e85Merge pull request #3862 from GeroZayas/docs/es-readme-sync-2025-10518daaadocs(es): sync README.es.md (macOS, 16 colors, Python 3.8+)cd5074fMerge pull request #3861 from Textualize/python314041406cremoved asv655b521test fixes27c2d2dbump for Python3.14ea9d4dbUpdate feature_request.md2dca1b7Merge pull request #3808 from Textualize/bump141019b6dddversion bumpYou can trigger a rebase of this PR by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)