Detect dependency-activated extra conflicts - #67
Draft
zanieb wants to merge 1 commit into
Draft
Conversation
zaniebot
force-pushed
the
zb/bughunt100/055-transitive-extra-conflicts
branch
from
July 16, 2026 02:41
4ae7406 to
fd80a23
Compare
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.
Conflicts involving extras enabled by dependencies can be missed, which can select incompatible versions or omit requested dependencies. Check declared conflicts after determining which projects, extras, and groups are enabled.
The dependency-group activation issue is reported in uv#19106, and incorrect conflict detection for selected workspace packages is tracked in uv#14848. Keep the workspace-member behavior from uv#18888.