Hello,

Unfortunately the deployment changes were more breaking than expected

I'm afraid that this is fixed with a post_install for everyone that uses Alamofire as a dependency on a Podfile.

But this is not the same as having a pod with a dependency on it, as cocoapods needs to lint the spec, and iOS 10 is one of the deployment targets that is not valid on Xcode 14.3 anymore, every single pod lib lint will fail, as it needs iOS 11.0 and beyond, like you can see on this PR discussion: mxcl/PromiseKit#1318 (comment)

So we have a chicken and egg problem here 😅

Could a major version fix this? And we can finally drop iOS 10?

iOS 10 (and that generation) is still valid, it just produces a warning, unlike iOS 8. For integrators, the post_install hook can take care of that, and for libraries with dependencies, passing --allow-warnings allows linting and pushing to pass normally with no changes to the pod itself. Any dependent library can also set its deployment target to any higher value, so Alamofire being low isn't a limitation.

The simple fact of the matter is that Apple will keep arbitrarily updating the minimum supported deployment target in Xcode whenever they want, and doing a major release to match every time that happens isn't tenable. If there's an actual breaking change, not simply a CocoaPod issue, then a major release may make sense.

Thank you so much for confirming @jshier, that's true, and I confirmed here with a lint, it's indeed a warning.

Let me get from here 😄