Skip to content

New resolver config - #1322

Closed
LalatenduMohanty wants to merge 5 commits into
mainfrom
new-resolver-config
Closed

New resolver config#1322
LalatenduMohanty wants to merge 5 commits into
mainfrom
new-resolver-config

Conversation

@LalatenduMohanty

Copy link
Copy Markdown
Member

Pull Request Description

What

Why

LalatenduMohanty and others added 5 commits August 14, 2026 09:51
…er` PBI property

Uncomment the `source: SourceResolver | None` field on both
`PackageSettings` and `VariantInfo`, add `SourceResolver` to the
public API, and wire up a `PackageBuildInfo.source_resolver` property
with variant-then-package fallback.

This is the foundation for all downstream resolver-config wiring
(Phases 2-9 of the new resolver config epic).

Closes: #1291
Co-Authored-By: Claude <claude@anthropic.com>
Signed-off-by: Lalatendu Mohanty <lmohanty@redhat.com>
…lidator_nrc

feat(packagesettings): activate source field and add source_resolver PBI property
…th set

Prevent confusing configs where the new `source` field silently
overrides legacy fields. Package-level `source` now conflicts with
`download_source` and `resolver_dist`; variant-level `source`
conflicts with `wheel_server_url` and `pre_built`.

Closes: #1207
Co-Authored-By: Claude <claude@anthropic.com>
Signed-off-by: Lalatendu Mohanty <lmohanty@redhat.com>
…lidator_nrc

feat(packagesettings): error when source and legacy settings are both set
@LalatenduMohanty
LalatenduMohanty requested a review from a team as a code owner September 10, 2026 12:59
@mergify mergify Bot added the ci label Sep 10, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant