Changes in Gemfile

8daa3bcb - [tools] Remove ethon override (#23543)

Mon, 17 Jul 2023 13:38:37 +0000

[tools] Remove ethon override (#23543) List of files: /expo/Gemfile

aae3986d - Update CocoaPods to 1.12.1 (#22238)

Mon, 24 Apr 2023 09:22:51 +0000

Update CocoaPods to 1.12.1 (#22238)Co-authored-by: Tomasz Sapeta List of files: /expo/Gemfile

9e4ebed2 - [fastlane] Bump version

Tue, 26 Apr 2022 01:19:53 +0000

[fastlane] Bump version List of files: /expo/Gemfile

08b7e930 - Update CocoaPods to 1.11.2

Sun, 07 Nov 2021 18:57:09 +0000

Update CocoaPods to 1.11.2 List of files: /expo/Gemfile

b06bc4e0 - Update fastlane

Tue, 05 Oct 2021 05:19:33 +0000

Update fastlane List of files: /expo/Gemfile

45bef721 - Update CocoaPods to 1.11.0 (#14378)

Fri, 10 Sep 2021 19:44:12 +0000

Update CocoaPods to 1.11.0 (#14378) List of files: /expo/Gemfile

6700d240 - [ios] Update CocoaPods to 1.10.2 (#14037)

Thu, 12 Aug 2021 17:15:33 +0000

[ios] Update CocoaPods to 1.10.2 (#14037) List of files: /expo/Gemfile

40530249 - [gemfile] Update ethon to avoid segmentation fault crashes on M1

Fri, 11 Jun 2021 10:27:43 +0000

[gemfile] Update ethon to avoid segmentation fault crashes on M1 List of files: /expo/Gemfile

98cc5488 - [ios] Upgrade CocoaPods to 1.10.1

Sat, 13 Feb 2021 16:37:57 +0000

[ios] Upgrade CocoaPods to 1.10.1 List of files: /expo/Gemfile

bbfaa29f - [repo] Upgrade Ruby dependencies (#11044)

Tue, 17 Nov 2020 15:22:34 +0000

[repo] Upgrade Ruby dependencies (#11044)# Why I noticed Ruby got recently upgraded — https://github.com/expo/expo/commit/32491227db0716485556d996dd390f76d0963599. So I installed the recommended version. Then I went to see if pod installation still works with new Ruby and noticed the installed CP version prints many unnecessary warnings like ``` /Users/sjchmiela/Applications/expo/.direnv/ruby/gems/cocoapods-core-1.9.3/lib/cocoapods-core/cdn_source.rb:342: warning: URI.escape is obsolete ``` Then I checked out CocoaPods releases, noticed there's one we could upgrade to, upgraded and here we are. # How Updated versions in `Gemfile` to latest, ran `bundle install` and then `pod install` in both `ios` directories in the repository. # Test Plan I have verified Expo Client compiles and runs. List of files: /expo/Gemfile

03170ecb - [repo] update fastlane to 2.159.0

Fri, 11 Sep 2020 01:15:45 +0000

[repo] update fastlane to 2.159.0 List of files: /expo/Gemfile

72e735a9 - Update CocoaPods to 1.9.3

Fri, 31 Jul 2020 09:59:19 +0000

Update CocoaPods to 1.9.3Podfile locks have already been generated with this version List of files: /expo/Gemfile

131ae183 - Update fastlane to 2.149.1

Thu, 18 Jun 2020 08:24:56 +0000

Update fastlane to 2.149.1 List of files: /expo/Gemfile

539625ca - [repo] Upgrade CocoaPods and Fastlane (#8560)

Mon, 01 Jun 2020 08:25:50 +0000

[repo] Upgrade CocoaPods and Fastlane (#8560)# Why When running `git pull` I noticed a strangely long output mentioning a lot of new `.xcconfig`s so I went to see when and why they were added. The commit adding them was [Publish expo-permissions, expo-notifications](https://github.com/expo/expo/commit/264a8722e01eb91cf1ec20eb5bdd09dd26fb829d). This does not sound like a commit that willingly upgrades CocoaPods used throughout the repository (which it did), so I decided to: - fix the long-standing problem of `pod` being used not-from-the-bundle - upgrade CocoaPods and Fastlane while I'm at it # How - updated version requirement for CocoaPods to `~> 1.9.1` - had to run `gem install bundler:2.1.4` even though I thought I've already run this command some time before - ran `bundle install` to install new CocoaPods - updated version requirement for Fastlane to `~> 2.148.0` - ran `bundle install` to install new CocoaPods - added `pod` and `fastlane` executables to the `bin` directory that are similar to `lock` executable—they are like an alias that makes `pod ` resolve to `bundle exec pod ` which should ensure that `pod` commands will fail if they would not resolve to the version installed by the bundler (In fact, `bundle install` installs its own executable commands under `.direnv/bin/`, but… you first have to run `bundle install` to have them, fail on `bundle exec pod…` should make it clear for the developers to install pods this way.) This commit also updates Pods of `react-native-safe-area-context` in `bare-expo`. # Test Plan - Ran `where pod`, verified that `/Users/sjchmiela/Applications/expo/bin/pod` is on the list. - Ran `bundle exec pod install` in `ios`, verified that it installs pods properly - Ran `pod install`, verified that it installs pods properly List of files: /expo/Gemfile

f7c5030c - [workspace] Install extra Ruby deps (#7851)

Wed, 15 Apr 2020 08:52:39 +0000

[workspace] Install extra Ruby deps (#7851)# Why We want to keep a single version of `cocoapods` and `xcpretty` among the contributors too. # How Added the `cocoapods` and `xcpretty` to root `Gemfile`. # Test Plan I have confirmed that once the gems are installed and we go out from the workspace and into, again, `pod` resolves to `pod` installed from the `Gemfile` (eg. `/Users/sjchmiela/Applications/expo/.direnv/bin/pod`). List of files: /expo/Gemfile

ef80677c - Remove nix

Tue, 07 Apr 2020 21:34:55 +0000

Remove nix List of files: /expo/Gemfile