Skip to content
Merged
Show file tree
Hide file tree
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
8 changes: 4 additions & 4 deletions pyproject.toml
Original file line number Diff line number Diff line change
Expand Up @@ -23,7 +23,7 @@ dependencies = [
"celery-redbeat==2.3.3",
"certifi==2026.1.4",
"clickhouse-connect==0.8.17",
"clickhouse-driver==0.2.9",
"clickhouse-driver==0.2.10",
"clickhouse-pool==0.5.3",
"circular-dict==1.9",
"cryptography==46.0.7",
Expand Down Expand Up @@ -89,13 +89,13 @@ dependencies = [
"more-itertools==9.0.0",
"nanoid==2.0.0",
"natsort==8.4.0",
"nh3==0.2.14",
"nh3==0.3.5",
"numpy~=2.1.0",
"openai==1.109.1",
"openpyxl==3.1.2",
"openpyxl==3.1.5",
"orjson==3.11.6",
"pandas~=2.2.2",
"paramiko==3.4.1",
"paramiko~=3.5.0",
Comment thread
webjunkie marked this conversation as resolved.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

maintainability (P3): paramiko changed from exact pin (==3.4.1) to compatible-release specifier (~=3.5.0), allowing automatic patch bumps within 3.5.x. This is inconsistent with most other deps in this file that use == pins. Intentional loosening is fine if desired, but worth confirming.

Prompt for AI agents
Check if this issue is valid β€” if so, understand the root cause and fix it. At pyproject.toml, line 98:

<issue>
paramiko changed from exact pin (`==3.4.1`) to compatible-release specifier (`~=3.5.0`), allowing automatic patch bumps within 3.5.x. This is inconsistent with most other deps in this file that use `==` pins. Intentional loosening is fine if desired, but worth confirming.
</issue>

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

maintainability (P3): paramiko changed from exact pin (==3.4.1) to compatible-release specifier (~=3.5.0). The lockfile still pins to 3.5.1, but this allows minor version drift on re-lock. Other dependencies in this file use exact pins β€” consider keeping consistency.

Prompt for AI agents
Check if this issue is valid β€” if so, understand the root cause and fix it. At pyproject.toml, line 98:

<issue>
paramiko changed from exact pin (`==3.4.1`) to compatible-release specifier (`~=3.5.0`). The lockfile still pins to 3.5.1, but this allows minor version drift on re-lock. Other dependencies in this file use exact pins β€” consider keeping consistency.
</issue>

"pillow==12.2.0",
"protobuf~=5.29.6",
"posthoganalytics==7.13.0",
Expand Down
Loading
Loading