Elgato_dark/IGListKit
1
0
Fork 0
mirror of https://github.com/Instagram/IGListKit synced 2026-05-23 17:28:22 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions
IGListKit/Gemfile

9 lines
205 B
Text
Raw Normal View History

Add Gemfile and setup travis to cache the dependencies Summary: Issue fixed: #757 Added gems to a `Gemfile`, CocoaPods is part of the default [gem set](https://docs.travis-ci.com/user/reference/osx/#Gems-in-the-global-gem-set). - [ ] ~All tests pass. Demo project builds and runs.~ - [ ] ~I added tests, an experiment, or detailed why my change isn't tested.~ - [x] I added an entry to the `CHANGELOG.md` for any breaking changes, enhancements, or bug fixes. - [x] I have reviewed the [contributing guide](https://github.com/Instagram/IGListKit/blob/master/.github/CONTRIBUTING.md) Closes https://github.com/Instagram/IGListKit/pull/865 Reviewed By: ryanolsonk Differential Revision: D5562906 Pulled By: rnystrom fbshipit-source-id: fe14916644576d1eba9da540ef5a3c0e6294fa13
2017-08-04 21:53:58 +00:00
source 'https://rubygems.org'
Add explicit `activesupport` version as CocoaPods dependency (#1590) Summary: ## Changes in this pull request All of the tests started failing today with a cryptic Ruby error. It turns out that a new version of `activesupport`, a dependency of CocoaPods was released and it introduced a bug. CocoaPods wasn't referencing a direct version of `activesupport` required, and so it was automatically trying to pull in this new invalid version. This PR fixes the issue by explicitly specifying the last known good version of the dependency in the `Gemfile`. ### Checklist - [x] All tests pass. Demo project builds and runs. - [x] I added tests, an experiment, or detailed why my change isn't tested. - [x] I added an entry to the `CHANGELOG.md` for any breaking changes, enhancements, or bug fixes. - [x] I have reviewed the [contributing guide](https://github.com/Instagram/IGListKit/blob/main/.github/CONTRIBUTING.md) Pull Request resolved: https://github.com/Instagram/IGListKit/pull/1590 Test Plan: Tested and confirmed on my own fork of IGListKit this resolves the CocoaPods issue Reviewed By: fabiomassimo Differential Revision: D50013182 Pulled By: TimOliver fbshipit-source-id: 623eab49dea5ff0b589b6f06ce589e99873dece4
2023-10-12 04:30:06 +00:00
gem "activesupport", "= 7.0.8"
Update build environment to latest OS versions Summary: Our CI harness for IGListKit on GitHub recently started to consistently fail at the unit test phase (https://github.com/Instagram/IGListKit/actions/runs/4683650178/jobs/8298963444). After researching it, it looks like GitHub Actions changed some configurations with their older versions of macOS, and our existing build script no longer seems to be working now. The build output seems to imply that Xcode simply hangs when it gets to the testing phase. I decided to take this chance to do a thorough audit of all our build steps and update as many of the dependencies as I could to their latest versions. This has fixed the issue, and hopefully given us a decent amount of future-proofing at the same time. :) Reviewed By: candance Differential Revision: D45002141 fbshipit-source-id: 40b22da4a9282900ff299b5e41f3a8566c4071f0
2023-04-18 03:41:49 +00:00
gem 'cocoapods', '~> 1.12.0'
Updated and reintegrated Danger into GitHub Actions CI Summary: Danger is the build tool we've been using to proof-check incoming PRs, including making sure the incoming change is properly documented, and if needed, running SwiftLint on incoming Swift code. Danger was originally running in our Travis CI implementation, but it wasn't integrated when we switched to GitHub Actions. This diff updates our Danger dependencies to the latest versions, and integrates Danger into our CI system as a separate build step. I've also modified its SwiftLint setup so it will now lint Swift files in both our sample apps, and the Swift source files in `IGListSwiftKit` itself. Reviewed By: candance Differential Revision: D43265158 fbshipit-source-id: 8939b821af36b544fe4d66662b6ce0f99a8f768c
2023-03-01 02:53:02 +00:00
gem 'danger', '~> 9.2.0'
Update build environment to latest OS versions Summary: Our CI harness for IGListKit on GitHub recently started to consistently fail at the unit test phase (https://github.com/Instagram/IGListKit/actions/runs/4683650178/jobs/8298963444). After researching it, it looks like GitHub Actions changed some configurations with their older versions of macOS, and our existing build script no longer seems to be working now. The build output seems to imply that Xcode simply hangs when it gets to the testing phase. I decided to take this chance to do a thorough audit of all our build steps and update as many of the dependencies as I could to their latest versions. This has fixed the issue, and hopefully given us a decent amount of future-proofing at the same time. :) Reviewed By: candance Differential Revision: D45002141 fbshipit-source-id: 40b22da4a9282900ff299b5e41f3a8566c4071f0
2023-04-18 03:41:49 +00:00
gem 'danger-swiftlint', '~> 0.32.0'
Integrate Slather into GitHub Actions CI Summary: Slather is the utility we've been using to upload our code coverage stats up to Coveralls. It was omitted from our GitHub CI file (Quite possibly because Slather didn't support GitHub Actions at the time), and so our most recent Coverall stats are from April 2020. This diff integrates Slather into our GitHub Actions CI pipeline. I had to modify the `xcodebuild` commands to remove the GCC settings since having them in there was producing completely empty coverage files. I'm assuming they were necessary for our previous CI setup, but it seems it's okay to drop them now. Reviewed By: DimaVartanian Differential Revision: D42995789 fbshipit-source-id: 7a86e262da8bc70b6da1e627a3f0ceb83348db27
2023-02-09 05:51:25 +00:00
gem 'slather', '~> 2.7.4'
Update build environment to latest OS versions Summary: Our CI harness for IGListKit on GitHub recently started to consistently fail at the unit test phase (https://github.com/Instagram/IGListKit/actions/runs/4683650178/jobs/8298963444). After researching it, it looks like GitHub Actions changed some configurations with their older versions of macOS, and our existing build script no longer seems to be working now. The build output seems to imply that Xcode simply hangs when it gets to the testing phase. I decided to take this chance to do a thorough audit of all our build steps and update as many of the dependencies as I could to their latest versions. This has fixed the issue, and hopefully given us a decent amount of future-proofing at the same time. :) Reviewed By: candance Differential Revision: D45002141 fbshipit-source-id: 40b22da4a9282900ff299b5e41f3a8566c4071f0
2023-04-18 03:41:49 +00:00
gem 'xcpretty', '~> 0.3.0'
Reference in a new issue Copy permalink