feat: implement v3 repodata/matchspec support for pixi and pixi-build#5998
Open
wolfv wants to merge 6 commits intoprefix-dev:mainfrom
Open
feat: implement v3 repodata/matchspec support for pixi and pixi-build#5998wolfv wants to merge 6 commits intoprefix-dev:mainfrom
wolfv wants to merge 6 commits intoprefix-dev:mainfrom
Conversation
wolfv
force-pushed
the
v3-matchspec-repodata
branch
from
185b305 to
85e96f7
Compare
wolfv
commented
May 2, 2026
|
|
||
| fn on_unsupported_repodata_revision(&mut self, message: &UnsupportedRepodataRevision) { | ||
| let message = message.to_string(); | ||
| if self.unsupported_revision_warnings.insert(message.clone()) { |
Member
Author
There was a problem hiding this comment.
This will print a warning when v4 ... and any future versions appear (assuming that our scheme gets accepted by CEP).
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.
Description
feat: wire v3 repodata fields through pixi build
Map v3 MatchSpec fields into PixiSpec and build protocol specs, and preserve extras, flags, conditions, license family, and track features across build backend conversions.
Pass through recipe extra_depends and build flags into source records, enable v3 rattler-build output configuration, and parse v3 MatchSpec syntax where pixi consumes dependency strings.
Questions
Should we, in fact, wire through
track-featuresandlicense? Might be noisy.How Has This Been Tested?
Not yet, will do.
AI Disclosure
Tools: Claude
Checklist:
schema/model.py.