🔒 🤖 CI Update pixi lock file 🔒 🤖#2183
Closed
skrub-bot wants to merge 1 commit into
Closed
Conversation
skrub-bot
force-pushed
the
auto-update-pixi-lock-file
branch
from
4d5051b to
b66522a
Compare
Member
|
Tests are failing because of a deprecation warning that will be addressed in #2173, and the lock file will also be updated there |
Member
|
it's just a question of removing a test so worth not tying this update to 2173 which is bigger and unrelated. i'll push the fix & merge |
Merged
Member
|
superseded by #2184 |
This file contains hidden or 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
4 participants
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.
Update lock files.
Note
If the CI tasks fail, create a new branch based on this PR and add the required fixes to that branch.