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
It is actually nice to not have the version stored in the lock file. See for instance ComPWA/ampform#446, where the uv.lock had to be updated after AmpForm got a new release tag.
Since
uv
v0.5.19, the version of an editable package that dynamically sets the version (e.g. withsetuptools-scm
) is not stored to theuv.lock
file anymore. This results in problems like these:https://github.com/ComPWA/ampform/actions/runs/12827104659/job/35770965965
It is actually nice to not have the version stored in the lock file. See for instance ComPWA/ampform#446, where the
uv.lock
had to be updated after AmpForm got a new release tag.The following repositories have
uv.lock
files:https://github.com/search?q=org%3AComPWA+path%3A%2F%5Euv.lock%24%2F&type=code
and these projects set
setuptools-scm
to remove the commit from the version:https://github.com/search?q=org%3AComPWA+path%3Apyproject.toml+%2Flocal_scheme+%3D+%22no-local-version%22%2F&type=code
Creating a PR for these is quite simple. First, make sure you have the latest version of
uv
and your installed tools likepre-commit-uv
andtox-uv
:then create a branch, update all the lock files, and create a PR:
Tasks
is_integer()
bug for QRules v0.10.4 ampform#450The text was updated successfully, but these errors were encountered: