Put Julia directly in the Pixi environment - #1017
Merged
Merged
Conversation
Prevent future lockfile updates from selecting a Julia package from another configured channel. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
SouthEndMusic
pushed a commit
to Deltares/Ribasim
that referenced
this pull request
Jul 28, 2026
## Summary - install Julia 1.12.6 directly from the `julia-forge` Pixi channel on all supported platforms - explicitly pin Julia to `julia-forge` so future solves cannot select another channel - remove redundant JuliaUp preparation from CI workflows - let VS Code use Julia from the activated Pixi environment This follows the approach from Deltares/Wflow.jl#1017. Linux ARM64 packages were enabled upstream in wolfv/julia-forge#7, allowing Ribasim to use one Julia dependency across all four platforms without a JuliaUp fallback. ## Validation - `pixi search julia -c https://prefix.dev/julia-forge --platform linux-aarch64` - `pixi lock` across all four supported platforms - `pixi run --locked julia --version` (`1.12.6`) - verified every locked Julia package comes from `julia-forge` - `pixi run prek run --files pixi.toml pixi.lock` - `git diff --check` --------- Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
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.
We had juliaup from conda-forge in our Pixi workspace. That did not directly install the julia version we needed in the environment, it just installed juliaup, and we had to remember to run
pixi run install-juliawhich installed the right julia version and set the Wflow directory as a juliaup override. This is easy to forget and feels a bit two-staged.https://prefix.dev/ has the julia-forge channel, which contains the same julia binaries that juliaup serves: https://prefix.dev/channels/julia-forge/packages/julia. If we use this, we directly have the right julia in our pixi environment. The Julia dependency is explicitly pinned to the
julia-forgechannel, so future lockfile updates cannot select Julia from another configured channel.So I did essentially this:
Then I could remove
pixi run install-juliafrom the CI jobs, since it is no longer needed. At first I thought I'd removeinstall-juliacompletely, but kept it for now. Because if developers are used to runningjuliainstead ofpixi run julia, or activating their pixi environment, then they may get the wrong version. We can always remove it later on as well.