Update CocoaPods guidance to reflect current version#10073
Open
kevnm67 wants to merge 1 commit intocircleci:mainfrom
Open
Update CocoaPods guidance to reflect current version#10073kevnm67 wants to merge 1 commit intocircleci:mainfrom
kevnm67 wants to merge 1 commit intocircleci:mainfrom
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Updated the CocoaPods optimization section to remove outdated version references and reflect the current CocoaPods version shipped in the macOS image.
Reasons
The existing guidance cited CocoaPods 1.8 as the minimum recommended version, which is outdated. Updated the copy to reflect the current version shipped in the Xcode 26.3.0 image (
1.16.2) so contributors have an accurate, up-to-date reference.Content checks
Preview your changes:
ci/circleci: lintjob at the bottom of your PR.ci/circleci: buildjob at the bottom of your PR.Content structure:
Formatting: