You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
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!
Activity
woile commentedon Jan 31, 2025
Should we extend
pep440
to detect the presence ofuv.lock
?feat(providers): add uv_provider
Lee-W commentedon Jan 31, 2025
yep, sounds like a good idea!
lsorber commentedon Feb 17, 2025
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 causesuv.lock
to be out of sync withpyproject.toml
.Until Commitizen supports
uv.lock
, would you recommend addinguv lock --offline
to the pre_bump_hooks as a workaround?feat(providers): add uv_provider
feat(providers): add uv_provider
feat(providers): add uv_provider
Lee-W commentedon Feb 18, 2025
yep, that could be a workaround. I just wrap up my PR #1351. I think we can have this feature soon!
7 remaining items