| #
8daa3bcb |
| 17-Jul-2023 |
James Ide <[email protected]> |
[tools] Remove ethon override (#23543)
|
| #
aae3986d |
| 24-Apr-2023 |
Tomasz Sapeta <[email protected]> |
Update CocoaPods to 1.12.1 (#22238)
Co-authored-by: Tomasz Sapeta <[email protected]>
|
| #
9e4ebed2 |
| 26-Apr-2022 |
Brent Vatne <[email protected]> |
[fastlane] Bump version
|
| #
08b7e930 |
| 07-Nov-2021 |
Tomasz Sapeta <[email protected]> |
Update CocoaPods to 1.11.2
|
| #
b06bc4e0 |
| 05-Oct-2021 |
Brent Vatne <[email protected]> |
Update fastlane
|
| #
45bef721 |
| 10-Sep-2021 |
Tomasz Sapeta <[email protected]> |
Update CocoaPods to 1.11.0 (#14378)
|
| #
6700d240 |
| 12-Aug-2021 |
Tomasz Sapeta <[email protected]> |
[ios] Update CocoaPods to 1.10.2 (#14037)
|
| #
40530249 |
| 11-Jun-2021 |
Tomasz Sapeta <[email protected]> |
[gemfile] Update ethon to avoid segmentation fault crashes on M1
|
| #
98cc5488 |
| 13-Feb-2021 |
Tomasz Sapeta <[email protected]> |
[ios] Upgrade CocoaPods to 1.10.1
|
| #
bbfaa29f |
| 17-Nov-2020 |
Stanisław Chmiela <[email protected]> |
[repo] Upgrade Ruby dependencies (#11044)
# Why
I noticed Ruby got recently upgraded — https://github.com/expo/expo/commit/32491227db0716485556d996dd390f76d0963599. So I installed the recommended
[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.
show more ...
|
| #
03170ecb |
| 11-Sep-2020 |
Eric Samelson <[email protected]> |
[repo] update fastlane to 2.159.0
|
| #
72e735a9 |
| 31-Jul-2020 |
Tomasz Sapeta <[email protected]> |
Update CocoaPods to 1.9.3
Podfile locks have already been generated with this version
|
| #
131ae183 |
| 18-Jun-2020 |
Tomasz Sapeta <[email protected]> |
Update fastlane to 2.149.1
|
| #
539625ca |
| 01-Jun-2020 |
Stanisław Chmiela <[email protected]> |
[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. T
[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 <X>` resolve to `bundle exec pod <X>` 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
show more ...
|
| #
f7c5030c |
| 15-Apr-2020 |
Stanisław Chmiela <[email protected]> |
[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 ro
[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`).
show more ...
|
| #
ef80677c |
| 07-Apr-2020 |
Nick Novitski <[email protected]> |
Remove nix
|