MAINT: Set requires-pixi in pixi.toml#11154
Merged
jsignell merged 2 commits intopydata:mainfrom Feb 23, 2026
Merged
Conversation
github-actions
bot
added
topic-documentation
Automation
We don't have to pin the pixi version in the workflow - compatability of Pixi versions can be managed by Pixi itself.
VeckoTheGecko
force-pushed
the
requires-pixi
branch
from
3e54454 to
173e6bd
Compare
jsignell
approved these changes
Feb 23, 2026
Member
jsignell
left a comment
jsignell
left a comment
There was a problem hiding this comment.
This looks fine to me. Do we need a plan to keep the pixi version in the Dockerfile in sync with pixi.toml?
Contributor
Author
Nope :) . I think I was the only one using the dockerfile anyway. If it gets out of sync, someone can raise an issue manually - the error message will be very clear anyway (can you merge? I don't have access yet) |
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
2 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.
I recently found the
requires-pixifield in thepixi.tomlWe don't have to pin the pixi version in the workflow - compatability of Pixi versions can be enforced by Pixi itself.
cc @keewis
I think for robustness we'd probably want Parcels-code/pixi-lock#13 as well - let me know if that's a blocker for this PR.not needed