Add uv provider #1349

Activity

1. Lee-W

   added

   type: featureA new enhacement proposalA new enhacement proposal

   issue-status: wait-for-implementationmaintainers agree on the bug / featuremaintainers agree on the bug / feature

   good first issue

   on Jan 31, 2025
2. github-actions

   added

   issue-status: needs-triage

   on Jan 31, 2025
3. Lee-W

   removed

   issue-status: needs-triage

   on Jan 31, 2025
4. woile commented on Jan 31, 2025

   

   woile

   on Jan 31, 2025

   Member

   More actions

   Should we extend pep440 to detect the presence of uv.lock?
5. Lee-W

   added a commit that references this issue on Jan 31, 2025

   feat(providers): add uv_provider

   ...

   This issue will close once commit b76cefb is merged into the 'master' branch.

   b76cefb
6. Lee-W commented on Jan 31, 2025

   

   Lee-W

   on Jan 31, 2025

   MemberAuthor

   More actions

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

   yep, sounds like a good idea!
7. lsorber commented on Feb 17, 2025

   

   lsorber

   on Feb 17, 2025

   More actions

   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?
8. Lee-W

   added 3 commits that reference this issue on Feb 18, 2025

   feat(providers): add uv_provider

   ...

   This issue will close once commit 82ab93c is merged into the 'master' branch.

   82ab93c

   feat(providers): add uv_provider

   ...

   This issue will close once commit 0283e7c is merged into the 'master' branch.

   0283e7c

   feat(providers): add uv_provider

   ...

   This issue will close once commit 1fa1b7c is merged into the 'master' branch.

   1fa1b7c
9. Lee-W commented on Feb 18, 2025

   

   Lee-W

   on Feb 18, 2025

   MemberAuthor

   More actions

   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!
10. Lee-W

    added a commit that references this issue on Feb 28, 2025

    feat(providers): add uv_provider

    ...

    This issue will close once commit 839d108 is merged into the 'master' branch.

    839d108
11. Lee-W

    closed this as completedin #1351on Feb 28, 2025
12. Lee-W

    closed this as completedin 7805412on Feb 28, 2025
13. khrapovs commented on Feb 28, 2025

    

    khrapovs

    on Feb 28, 2025

    More actions

    Thank you so much for this, I've been waiting for it! But unfortunately you have forgotten to document it for the users like me ;) I think this feature deserves to be mentioned in https://commitizen-tools.github.io/commitizen/config/#version-providers :)
14. pull

    added a commit that references this issue on Feb 28, 2025

    feat(providers): add uv_provider

    ...

    This issue will close once commit 7805412 is merged into the 'master' branch.

    7805412
15. Lee-W commented on Mar 2, 2025

    

    Lee-W

    on Mar 2, 2025

    MemberAuthor

    More actions

    Thank you so much for this, I've been waiting for it! But unfortunately you have forgotten to document it for the users like me ;) I think this feature deserves to be mentioned in https://commitizen-tools.github.io/commitizen/config/#version-providers :)

    yep, miss this part 🤦‍♂️. just sent a PR for it
    #1362