chore(dependencies): Switch from tool.uv.dev-dependencies to dependency-groups.dev #518

luke · 2025-10-13T15:25:35Z

luke commented

2025-10-13 15:25:35 +00:00

warning: The tool.uv.dev-dependencies field (used in pyproject.toml) is deprecated and will be removed in a future release; use dependency-groups.dev instead

warning: The `tool.uv.dev-dependencies` field (used in `pyproject.toml`) is deprecated and will be removed in a future release; use `dependency-groups.dev` instead

luke added 1 commit 2025-10-13 15:25:37 +00:00

Switch from tool.uv.dev-dependencies to dependency-groups.dev

Enforce Conventional Commit PR Title / Validate PR Title (pull_request_target) Failing after 8s

Details

CI / ci (pull_request) Successful in 4m16s

Details

42126f7937

warning: The `tool.uv.dev-dependencies` field (used in `pyproject.toml`) is deprecated and will be removed in a future release; use `dependency-groups.dev` instead

ai-review-bot commented

2025-10-13 15:25:48 +00:00

Decision: Reject
Change Score: 2/10

This diff proposes changes to the pyproject.toml file, specifically modifying how development dependencies are handled. The original uses a tool.uv section (likely for the uv package manager), while the proposed change shifts this to a dependency-groups section with a "dev" group.

Problems:

Non-Standard: The dependency-groups section with a dev group is not a standard or widely recognized way to specify development dependencies in pyproject.toml. Standard practice dictates using tool.poetry.dev-dependencies for Poetry or tool.pdm.dev-dependencies for PDM, or a similar tool-specific section. It's unclear what tool this configuration targets, making it potentially unusable and confusing.
Potential Tool Incompatibility: Introducing a non-standard section can lead to compatibility issues with various packaging tools. Many tools might ignore this section, rendering the specified development dependencies ineffective.
tool.uv Removal: Removing the tool.uv section implicitly suggests a shift away from using the uv package manager without explicitly stating the alternative. If the project intends to switch to a different tool, it should be clearly articulated and the configuration should align with the conventions of the new tool.

Recommendation:

Reject this change. Instead, clarify which packaging tool the project intends to use and adopt the corresponding standard configuration for development dependencies. If the project aims to use Poetry, the tool.poetry.dev-dependencies section should be used. Similarly, for PDM, the tool.pdm.dev-dependencies section should be used. If uv is intended, the configuration should remain within the tool.uv namespace.

Example (assuming Poetry):

[tool.poetry.dependencies]
python = "^3.8"
astroid = "<=4.0.1"

[tool.poetry.dev-dependencies]
black = "<25.9.1,>=25.9.0"
coverage = "<8.0.0,>=7.6.10"
isort = "<6.1.1,>=6.1.0"

or (assuming PDM):

[project]
dependencies = [
    "astroid<=4.0.1",
]

[tool.pdm]
dev-dependencies = { dev = ["black<25.9.1,>=25.9.0", "coverage<8.0.0,>=7.6.10", "isort<6.1.1,>=6.1.0"] }

**Decision: Reject** **Change Score: 2/10** This diff proposes changes to the `pyproject.toml` file, specifically modifying how development dependencies are handled. The original uses a `tool.uv` section (likely for the uv package manager), while the proposed change shifts this to a `dependency-groups` section with a "dev" group. Problems: 1. **Non-Standard:** The `dependency-groups` section with a `dev` group is not a standard or widely recognized way to specify development dependencies in `pyproject.toml`. Standard practice dictates using `tool.poetry.dev-dependencies` for Poetry or `tool.pdm.dev-dependencies` for PDM, or a similar tool-specific section. It's unclear what tool this configuration targets, making it potentially unusable and confusing. 2. **Potential Tool Incompatibility:** Introducing a non-standard section can lead to compatibility issues with various packaging tools. Many tools might ignore this section, rendering the specified development dependencies ineffective. 3. **`tool.uv` Removal:** Removing the `tool.uv` section implicitly suggests a shift away from using the `uv` package manager without explicitly stating the alternative. If the project intends to switch to a different tool, it should be clearly articulated and the configuration should align with the conventions of the new tool. Recommendation: Reject this change. Instead, clarify which packaging tool the project intends to use and adopt the corresponding standard configuration for development dependencies. If the project aims to use Poetry, the `tool.poetry.dev-dependencies` section should be used. Similarly, for PDM, the `tool.pdm.dev-dependencies` section should be used. If `uv` is intended, the configuration should remain within the `tool.uv` namespace. Example (assuming Poetry): ```toml [tool.poetry.dependencies] python = "^3.8" astroid = "<=4.0.1" [tool.poetry.dev-dependencies] black = "<25.9.1,>=25.9.0" coverage = "<8.0.0,>=7.6.10" isort = "<6.1.1,>=6.1.0" ``` or (assuming PDM): ```toml [project] dependencies = [ "astroid<=4.0.1", ] [tool.pdm] dev-dependencies = { dev = ["black<25.9.1,>=25.9.0", "coverage<8.0.0,>=7.6.10", "isort<6.1.1,>=6.1.0"] } ```

luke changed title from ~~Switch from tool.uv.dev-dependencies to dependency-groups.dev~~ to chore(dependencies): Switch from tool.uv.dev-dependencies to dependency-groups.dev

2025-10-13 15:26:49 +00:00

luke merged commit e41f35ca1f into main

2025-10-13 15:31:09 +00:00

luke deleted branch luke-patch-1

2025-10-13 15:31:11 +00:00

luke referenced this issue from a commit

2025-10-13 15:31:15 +00:00

chore(dependencies): Switch from tool.uv.dev-dependencies to dependency-groups.dev (#518)

Sign in to join this conversation.

2 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: repos/webexmemebot#518