Xcode SDK and CocoaPods: Deployment Target Synchronization During Upgrades

Updating the Xcode SDK often necessitates changes to the project's Deployment Target to maintain compatibility with new API requirements. However, Objective-C projects utilizing CocoaPods manage these targets across multiple configuration files, including the main project settings and the Podfile.

When the SDK is upgraded, a discrepancy can emerge between the project's target version and the version defined in the Podfile. This misalignment can lead to build-time failures or runtime instability if the dependency resolution does not align with the updated SDK constraints.

What is the recommended mechanism for ensuring the Podfile's platform version remains synchronized with the Xcode project's Deployment Target during an SDK migration? Does the current build system provide a way to automate this synchronization to prevent mismatched binary targets?