Skip to content

Conversation

@VeckoTheGecko
Copy link
Contributor

Previously CI was pulling in the latest Pixi version and running based on that. This occasionally creates failing builds in (e.g.,) lock generation.

It would be better to pin this so that we can keep local development in sync with CI and move together.

Changes:

  • Pin CI for pixi versions to latest pixi release (0.63.0)
  • Fix pixi.toml to be compatible with 0.63.0

@erikvansebille and @fluidnumerics-joe - you will need to update your pixi versions. If installed via brew: brew upgrade pixi

Comment on lines +25 to +26
with:
pixi-version: "v0.62.2" # keep in sync with env var above
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This wart in the code "keep in sync with above" is unfortunately necessary. Discussion about this and pinning of pixi versions in CI can be seen at pydata/xarray#10888 (comment)

@VeckoTheGecko
Copy link
Contributor Author

CI is now fixed. Merging so we can rebase the other PRs and so I can continue local development. Let me know if there is anything amiss with the PR and we can do a post-merge review 😅

@VeckoTheGecko VeckoTheGecko merged commit 557916c into v4-dev Jan 15, 2026
11 checks passed
@VeckoTheGecko VeckoTheGecko deleted the fix-pixi-toml branch January 15, 2026 10:03
@github-project-automation github-project-automation bot moved this from Backlog to Done in Parcels development Jan 15, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

2 participants