Detect dependency-activated extra conflicts - #78
Closed
zaniebot wants to merge 1 commit into
Closed
Conversation
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
2 participants
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.
A root group or package conflicting with a dependency-activated extra can pass preflight, allowing
uv syncoruv exportto select incompatible versions or silently omit a requested subtree. Enforce declared conflicts against materialized active projects, extras, and groups.Workspace activation/conflict regressions are reported in uv#19106 and uv#14848; preserve the materialized-member semantics tightened in uv#18888.
Moved to: astral-sh/uv-dev#67.