feat: read the shared config layer instead of pixi's config files - #2724
Draft
Hofer-Julian wants to merge 1 commit into
Draft
feat: read the shared config layer instead of pixi's config files#2724Hofer-Julian wants to merge 1 commit into
Hofer-Julian wants to merge 1 commit into
Conversation
Hofer-Julian
force-pushed
the
shared-config-layer
branch
2 times, most recently
from
August 5, 2026 14:26
a33c377 to
d8fd045
Compare
rattler-build reads the shared rattler configuration (`/etc/rattler/config.toml`, `$XDG_CONFIG_HOME/rattler/config.toml`) layered with its own files. Pixi's config files are no longer read: they warned about every pixi-only key and leaked pixi settings like `default-channels` into builds. Settings meant for every tool belong in the shared files. The rattler crates are temporarily patched to a conda/rattler git revision until a rattler_config with the shared layer is released.
Hofer-Julian
force-pushed
the
shared-config-layer
branch
from
August 5, 2026 14:45
d8fd045 to
0b454c1
Compare
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
1 participant
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.
Pixi and Rattler-Build understand largely the same settings: mirrors, S3 options, default channels, TLS. With conda/rattler#2645 there's a shared home for these config keys:
/etc/rattler/config.tomland$XDG_CONFIG_HOME/rattler/config.toml.Rattler-Build reads the shared layer plus its own files. Pixi's config files are no longer read: they warned about every pixi-only key and leaked pixi settings like
default-channelsinto builds.Draft until conda/rattler#2645 is merged and released; the
[patch.crates-io]entries go away then.Note: the Windows jobs fail while the git pin is in place - cargo's git checkout of the rattler repo hits
path too longon Windows runners. This resolves itself when the pin is dropped after the release.