⬆️(deps): Update rich requirement from <15.0.0,>=14.2.0 to >=15.0.0,<16.0.0 in /apps/meeseeks_cli#112
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@v14.2.0...v15.0.0) --- updated-dependencies: - dependency-name: rich dependency-version: 15.0.0 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
bot
added
dependencies
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
| "meeseeks-tools>=0.0.9", | ||
| "prompt-toolkit>=3.0.47,<4.0.0", | ||
| "rich>=14.2.0,<15.0.0", | ||
| "rich>=15.0.0,<16.0.0", |
There was a problem hiding this comment.
🔴 Incompatible rich version constraints between meeseeks-cli and its dependency meeseeks-tools
meeseeks-cli now requires rich>=15.0.0,<16.0.0, but it depends on meeseeks-tools>=0.0.9 (line 14), which declares rich>=14.2.0,<15.0.0 at packages/meeseeks_tools/pyproject.toml:18. These two constraints have an empty intersection — no version of rich can satisfy both simultaneously. This will cause dependency resolution to fail on uv lock (or pip install). The uv.lock file was also not regenerated as part of this PR; it still shows rich pinned to 14.3.2 with the old specifier >=14.2.0,<15.0.0 for meeseeks-cli. The rich constraint in meeseeks-tools needs to be bumped to match, or meeseeks-cli's constraint should be reverted.
Prompt for agents
The rich version constraint in meeseeks-cli (>=15.0.0,<16.0.0) conflicts with the constraint in its transitive dependency meeseeks-tools (>=14.2.0,<15.0.0 at packages/meeseeks_tools/pyproject.toml:18). These ranges have no overlap so dependency resolution will fail.
To fix:
1. Also bump the rich constraint in packages/meeseeks_tools/pyproject.toml from '>=14.2.0,<15.0.0' to '>=15.0.0,<16.0.0' (or a compatible range).
2. Verify that meeseeks_tools code is compatible with rich 15.x (check for any breaking API changes).
3. Regenerate uv.lock by running 'uv lock' after updating both pyproject.toml files.
4. Check if any other workspace members also pin rich to <15 and update them too.
Was this helpful? React with 👍 or 👎 to provide feedback.
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
6ac483ccorrection458a910Merge pull request #4080 from Textualize/bump150082e06e0changelogd6556bcbump to 15.0.0ffe2edcMerge pull request #4079 from Textualize/inline-table-codecf3b5a1changelog77f0edbremove comments7ef2d05fix inline code in table cells19c67b9Merge pull request #4077 from Textualize/isattry494b795changelogDependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually 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 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)