Cocoapods 1.9

[djbe]

2 things of note:

• CDN sources, which allows us to get rid of the (still slow) step of downloading the full repo. We can now also cache the specs folder as it isn't as massive.
• generate_multiple_pod_projects and incremental_installation, which should reduce the amount of changes during pod install/update.

[SwiftGen-Eve]

	2 Warnings
⚠️	Big PR
⚠️	You should make sure that Podfile.lock and Package.resolved are changed in sync

Hey 👋 I'm Eve, the friendly bot watching over SwiftGen 🤖

Thanks a lot for your contribution!

---

Once you fix those tiny nitpickings above, we should be good to go! 🙌

ℹ️ I will update this comment as you add new commits

Generated by 🚫 Danger

[djbe]

Would you look at that, 4 seconds (without cache) 😆 🚗💨

[AliSoftware]

We should also remove the deprecated .swift-version from the repo and use the swift_versions DSL attribute in the podspec instead

[djbe]

Uhm we can add the swift_versions bit, but some users seem to need that file to be there, see #555.

[AliSoftware]

Other than the fact that we should stop probably caching the CDN (and thus winning some more CI time by avoiding to restore it when not needed), LGTM

[AliSoftware]

With CDN, is it really still worth it to cache the ~/.cocoapods folder? From experience on other repos it doesn't really seem to be much necessary anymore.

We already commit the Pods/ folder (and if we didn't, we could cache it) so it should be quite rare to have the need for the spec repo to be present and downloaded locally anyway, as it is now supposed to only be necessary during pod update (or if pod install needs to actually install pods that were missing in Pods/ and were not at a version that was matching was was locked in Podfile.lock, which in our case should never happen on CI)

[AliSoftware]

iow, if you remove those steps from CI, and as long as we still commit the Pods/ folder and that Podfile.lock and Pods/Manifest.lock are properly in sync, I think pod install is now a no-op that shouldn't even require the CDN to be cloned at all.
Maybe I'm wrong so don't hesitate to make some tests to validate that if unsure.

[AliSoftware]

🎉 This should get rid of the security risk issue too 👍

[AliSoftware]

I thought the risk of using cache for specs repo was that cache restoration (download+unzip) and save (zip + upload) would risk taking more time than cloning the CDN. But after looking into it, I see that cache restoration only takes 3s. So we might as well keep it