I am mostly playing with pixi here, but I prefer to to this in a "real" repo to get actual feedback from realistic use cases. The idea of this is described in https://github.com/prefix-dev/pixi/issues/909.
TL;DR: Every once in a while we want to update the pixi lock file, to ensure that the software does not stop working with new versions of the dependencies, while ensuring that the PRs continue to work with fixed versions of the dependencies (and avoid problems of PRs with red CI checks, even if the PR itself did not break anything).
I am mostly playing with pixi here, but I prefer to to this in a "real" repo to get actual feedback from realistic use cases. The idea of this is described in https://github.com/prefix-dev/pixi/issues/909.
TL;DR: Every once in a while we want to update the pixi lock file, to ensure that the software does not stop working with new versions of the dependencies, while ensuring that the PRs continue to work with fixed versions of the dependencies (and avoid problems of PRs with red CI checks, even if the PR itself did not break anything).
fyi @diegoferigo @flferretti this is a workflow that may be related to what we discussed in https://github.com/ami-iit/jaxsim/pull/93 .