Take into account changes in Package.resolved

[Ernest0-Production]

We use Tuist and Package.swift to install external dependencies. When we update a dependency, the Package.resolved file is updated.

It seems reasonable to consider changing this file so that selective caching works correctly.

The Tuist/.build directory is usually in .gitignore, so git diff will not be able to detect it.

[mikeger]

Hey @Ernest0-Production ,

thanks for the issue.

Let me check if I understand it correctly. You have a repository that contains a package:

• This package has external dependencies.
• This package has Pacakge.resolved checked into the repository

Then, when the test job is executed, Package.resolved might change due to a new version of an external package being used.

Your expectation is that the tool would mark all targets in the given package as changed.

Does it accurately reflect the idea/issue you have?

[Ernest0-Production]

Yes, that's right.

I will also add notes that this problem occur with a dependency that was supplied as xcframework. (binaryTarget)

[mikeger]

@Ernest0-Production can you check the version from this branch, if it matches the expectation? https://github.com/mikeger/XcodeSelectiveTesting/compare/50-package-resolved-to-affect-targets?expand=1

[Ernest0-Production]

@mikeger Hi! Thanks, this seems to be what we need.
We are waiting for this to be merged)

[mikeger]

Please check the next release: https://github.com/mikeger/XcodeSelectiveTesting/releases/tag/0.12.3