Skip to content

Make sure uv.lock in breeze corresponds to pyproject.toml #43684

Open
@potiuk

Description

@potiuk

When you manually modify breeze's pyproject.toml, the uv.lock might not correspond to the changes you've just added. Breeze manages installation automatically when you run it, so when you use uv tool it should use the .lock, so whenever we modify pyproject.toml we should also make sure uv sync is run to reflect that.

This can be done with a pre-commit. The uv sync should only modify lock if pyproject.toml changed (unles --frozen option is used for uv sync - so we should be able to safely run uv lock in pre-commit for breeze, just to make sure no changes in pyproject.toml should be reflected in the lock file.

Metadata

Metadata

Assignees

Labels

area:dev-envCI, pre-commit, pylint and other changes that do not change the behavior of the final codearea:dev-tools

Type

No type

Projects

Status

In progress

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions