Pedro Piñera Buendía

> This change would be breaking if introduced as is and should be marked as such in the Changelog. How could we introduce this change in a non-breaking manner?

@Ernest0-Production, where are you using that path in your manifests? For attributes that represent a reference to a file, Tuist hashes the file itself, not the path, so it doesn't...

I'm a bit confused. Once those paths are resolved to absolute paths, what we hash is the file/directory they point to, not the path itself, so unless I'm missing something,...

Thanks @Ernest0-Production for debugging this one. If you are up for it, feel free to go ahead with a contribution. Our binary cache functionality also does content-based hashing, so you...

@Ernest0-Production, we'd need to know what changed between the run that was cached and the run that failed. We have some environment information like the Swift version or the content...

@Ernest0-Production, thanks for the clarification. I agree that we should support caching across environments to speed up generation times. However, we did not implement the logic with that use case...

> I can assume that because **there might have been many directories** for my project on the CI (stored under each pull request), a rare situation occurred when two MD5...

> Thanks for the explanation! But it still seems that even with hashing working correctly, for deploying an environment on CI it is important to have control over all the...

@Ernest0-Production what would you suggest as an alternative to that MD5 approach to prevent collisions?

> Can't we just refuse to create a prefix directory? Could you expand?