Map conda channels to prefix.dev mirrors for pixi builds #967
+154
−2
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.
Summary
Enable sharded repodata for pixi-based container builds by automatically mapping well-known conda channels to their prefix.dev mirrors:
conda-forge→https://prefix.dev/conda-forgebioconda→https://prefix.dev/biocondaRationale
According to the prefix.dev blog post on sharded repodata, using prefix.dev mirrors provides significant performance improvements for package resolution:
The sharded repodata architecture splits package metadata into content-addressed shards (one per package name), enabling aggressive caching and faster downloads compared to monolithic
repodata.jsonfiles.Implementation
mapChannelsToPixiServers()method inPixiHelperto map known channels to prefix.dev mirrorscondaFileFromRequest()inContainerHelperto apply channel mapping only whenbuildTemplate == CONDA_PIXI_V1Test plan
PixiHelperTestContainerHelperTestverifying mapping is applied only for pixi builds🤖 Generated with Claude Code