New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update Package.Resolved for ReactiveSwift 3.0.0 #1531

Merged
merged 1 commit into from Jan 7, 2018

Conversation

Projects
None yet
3 participants
@lucas34
Member

lucas34 commented Jan 6, 2018

Link to issue #1470
We updated Package.Swift to ReactiveSwift 3.0.0 but not the Package.Resolved.

@lucas34 lucas34 referenced this pull request Jan 6, 2018

Merged

Bump ReactiveSwift to 3.0 #1470

@codecov-io

This comment has been minimized.

codecov-io commented Jan 6, 2018

Codecov Report

❗️ No coverage uploaded for pull request base (development@c9ddcb3). Click here to learn what that means.
The diff coverage is n/a.

Impacted file tree graph

@@              Coverage Diff               @@
##             development    #1531   +/-   ##
==============================================
  Coverage               ?   87.82%           
==============================================
  Files                  ?        5           
  Lines                  ?      156           
  Branches               ?        0           
==============================================
  Hits                   ?      137           
  Misses                 ?       19           
  Partials               ?        0

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update c9ddcb3...e908987. Read the comment docs.

@sunshinejr

And this one as well, thanks again!

@sunshinejr sunshinejr merged commit 067b9bf into Moya:development Jan 7, 2018

1 check passed

ci/circleci Your tests passed on CircleCI!
Details

@lucas34 lucas34 deleted the lucas34:PR/ReactiveSwift branch Jan 8, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment