Skip to content
Closed
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion apps/truss_cli/pyproject.toml
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,7 @@ dependencies = [
"truss-core>=0.0.10",
"truss-tools>=0.0.10",
"prompt-toolkit>=3.0.47,<4.0.0",
"rich>=14.2.0,<15.0.0",
"rich>=14.2.0,<16.0.0",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 Inconsistent rich upper bound: truss_cli allows <16.0.0 but its dependency truss_tools still requires <15.0.0

truss_cli widens rich to <16.0.0, but it depends on truss-tools>=0.0.10 (apps/truss_cli/pyproject.toml:14), which still constrains rich>=14.2.0,<15.0.0 (packages/truss_tools/pyproject.toml:18). The pip/uv resolver will intersect these to <15.0.0, so this change has no practical effect — rich 15.x still cannot be installed. If the intent is to support rich 15.x, truss_tools must also be updated. As-is, the constraint is misleading about actual version compatibility.

Prompt for agents
The rich upper bound was widened to <16.0.0 in truss_cli, but truss_tools (a direct dependency of truss_cli, see apps/truss_cli/pyproject.toml:14) still pins rich to <15.0.0 at packages/truss_tools/pyproject.toml:18. The dependency resolver will take the intersection, so the effective upper bound is still <15.0.0. To actually allow rich 15.x, update packages/truss_tools/pyproject.toml line 18 to also use <16.0.0. Then regenerate the lockfile with uv sync.
Open in Devin Review

Was this helpful? React with 👍 or 👎 to provide feedback.

"textual>=7.5.0,<9.0.0",
]

Expand Down
Loading