chore: Test if Package.swift is valid on CI for older tooling

[facumenzella]

Motivation

This PR aims to add a quick way of validating Package.swift. At least the version that are not tested on every PR (so probably only 5.7 and 5.8 are enough)

Tons of things failed on the last release #4692, and this was one of them.

I did it in different jobs because I wasn't sure how to swap Xcode versions, but happy to reuse the same job if someone knows how to. Didn't dig much into it

[nguyenhuy]

2 cents from a bystander:

This is nice! 5.15.0 didn't seem to go out smoothly to me (so was 5.14.0). Agree that the Swift package files should have been validated by CI per-commit.

Another problem I noticed is related to pbxproj. Any plan to stop tracking it (xcodeproj in general)? I myself encountered merge conflicts while working on my branches. It just doesn't scale as you welcome more developers and bots to the project.

Pinterest stopped tracking xcodeproj many many years ago. xcodegen works well for us. So did Tulsi back when we built with bazel.

Xcode 16's buildable folders looks promising. Perhaps you are holding out for it?

[facumenzella]

Another problem I noticed is related to pbxproj. Any plan to stop tracking it (xcodeproj in general)? I myself encountered merge conflicts while working on my branches. It just doesn't scale as you welcome more developers and bots to the project.

@nguyenhuy the plan is to integrate tuist at some point. So yes, it will eventually disappear =)

[nguyenhuy]

@facumenzella That's great to hear! If it was up to me I'd put it quite high on my list, because:

1. It has to be done anyways
2. It'll offer productivity boost from day one
3. It honestly isn't complicated to set up (speaking from my experience with XcodeGen and assuming it'd apply to Tuist). And you can timebox it.

But of course you all have the complete picture of the read map and priorities so it's your call.

[aboedo]

this is great! :chefskiss: