Update CocoaPods gem to match the version used in Podfile.lock - #17843
Merged
Conversation
AliSoftware
commented
Jan 31, 2022
|
|
||
| gem 'rake' | ||
| gem 'cocoapods', '~> 1.10' | ||
| gem 'cocoapods', '~> 1.11' |
Contributor
Author
There was a problem hiding this comment.
This was not strictly necessary, as the most important thing was to ensure the version which was locked in the Gemfile.lock lockfile (after running bundle update cocoapods) was the same as the one here, and that version 1.11.2 already fulfilled the ~> 1.10 semver requirement. But that doesn't hurt either and made sense to request this as minimum version anyway, so 🙃
AliSoftware
enabled auto-merge
January 31, 2022 16:54
jkmassel
approved these changes
Jan 31, 2022
|
You can trigger optional UI/connected tests for these changes by visiting CircleCI here. |
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
2 participants
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.
The version of CocoaPods used to generate the latest
Podfile.lock(as seen at the very end of saidPodfile.lock) is1.11.2, but the version of CocoaPods used in ourGemfile.lockwas still locked to1.10.1.This PR simply aligns the two, so that we ensure CI (and local builds) use a version of the gem (from
Gemfile.lock) at least as recent as the one that was used to generate latestPodfile.lock.h/t @leandroalonso for noticing this.