fix(cli): Prioritize local packages over registry versions#9540
Merged
fortmarek merged 2 commits intotuist:mainfrom Feb 20, 2026
Merged
fix(cli): Prioritize local packages over registry versions#9540fortmarek merged 2 commits intotuist:mainfrom
fortmarek merged 2 commits intotuist:mainfrom
Conversation
dae89d3 to
ea41551
Compare
Replace force unwrap with compactMap and refactor test to use .inTemporaryDirectory and .withMockedDependencies traits. Co-Authored-By: Claude Opus 4.6 <[email protected]>
fortmarek
approved these changes
Feb 20, 2026
Member
fortmarek
left a comment
There was a problem hiding this comment.
Thanks! Made just some minor adjustments, otherwise, looks great 💯
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.
Resolves this issue
Summary
This PR fixes an issue in Tuist’s SwiftPM graph loading where a registry package could take precedence over a local/path dependency when the same package is present from multiple sources (local, registry, and/or SCM). In practice, this could cause the generated Xcode project to link against the registry version even when a local dependency was explicitly declared.
Tuist now selects a single package per "identity group" using the following precedence:
This matches SwiftPM’s expected behavior:
and the behavior introduced on #7518
How I tested
tuist run generate --path ...on a project reproducing the scenario described in the forum link above, and confirmed the generated project uses the local package rather than the registry one after the fix.