Skip to content

Add uv provider #1349

Closed
Closed
@Lee-W

Description

@Lee-W

Description

support updating both pyprojec.toml and uv.lock

Possible Solution

No response

Additional context

No response

Additional context

No response

Activity

woile

woile commented on Jan 31, 2025

@woile
Member

Should we extend pep440 to detect the presence of uv.lock?

added a commit that references this issue on Jan 31, 2025
b76cefb
Lee-W

Lee-W commented on Jan 31, 2025

@Lee-W
MemberAuthor

Should we extend pep440 to detect the presence of uv.lock?

yep, sounds like a good idea!

lsorber

lsorber commented on Feb 17, 2025

@lsorber

We're using Commitizen for Substrate and we noticed that you cannot just run cz bump with a uv project because bumping the version number causes uv.lock to be out of sync with pyproject.toml.

Until Commitizen supports uv.lock, would you recommend adding uv lock --offline to the pre_bump_hooks as a workaround?

added 3 commits that reference this issue on Feb 18, 2025
82ab93c
0283e7c
1fa1b7c
Lee-W

Lee-W commented on Feb 18, 2025

@Lee-W
MemberAuthor

We're using Commitizen for Substrate and we noticed that you cannot just run cz bump with a uv project because bumping the version number causes uv.lock to be out of sync with pyproject.toml.

Until Commitizen supports uv.lock, would you recommend adding uv lock --offline to the pre_bump_hooks as a workaround?

yep, that could be a workaround. I just wrap up my PR #1351. I think we can have this feature soon!

7 remaining items

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      Add uv provider · Issue #1349 · commitizen-tools/commitizen