feat: pass repodata records to build backend#4252
Merged
ruben-arts merged 3 commits intoprefix-dev:mainfrom Aug 1, 2025
Merged
feat: pass repodata records to build backend#4252ruben-arts merged 3 commits intoprefix-dev:mainfrom
ruben-arts merged 3 commits intoprefix-dev:mainfrom
Conversation
ruben-arts
approved these changes
Aug 1, 2025
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
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.
This PR adds the repodata records of the packages that were installed into the
host/buildprefix to the protocol. This allows the build backend to deduce important information like the version of the installed python.The change to the build API is both forward- and backwards-compatible.
In the future we should also add why a particular dependency was introduced, e.g. was it introduced as a run export? We can add that later though. This should unblock work on the ROS backend.