Add periodic action to update pixi lock file #178
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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 prefix-dev/pixi#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 ami-iit/jaxsim#93 .