All Versions
97
Latest Version
Avg Release Cycle
62 days
Latest Release
45 days ago

Changelog History
Page 2

  • v14.0.0-alpha.1 Changes

    May 14, 2019

    ๐Ÿš€ This is an early pre-release version of Moya 14. This includes newest RxSwift & ReactiveSwift versions. Next pre-releases would have new version of Alamofire and potentially removed Result dependency.

    ๐Ÿ”„ Changelog

    ๐Ÿ”„ Changed

    • ๐Ÿ’ฅ Breaking Change Minimum version of RxSwift is now 5.0. #1846 by @LucianoPAlmeida.
    • ๐Ÿ’ฅ Breaking Change Minimum version of ReactiveSwift is now 6.0. #1849 by @sunshinejr.
  • v13.0.1 Changes

    May 01, 2019

    ๐Ÿ”„ Changelog

    ๐Ÿ›  Fixed

    • ๐Ÿ›  Fixed a problem where, while using stubbed responses, Moya would generate weird cancellation errors in the console. #1841 by @sunshinejr.
  • v13.0.0 Changes

    April 10, 2019

    ๐Ÿฑ Xcode 10.2, Swift 5.0 and more! ๐Ÿš€

    Full Changelog for Moya 13.0:

    Note: there are no changes between 13.0.0-beta.1 and 13.0.0.

    ๐Ÿ”„ Changed

    • ๐Ÿ’ฅ Breaking Change .mapImage() extension on Single and Observable now returns non-optional image. #1789, #1799 by @bjarkehs and @sunshinejr.
    • ๐Ÿ’ฅ Breaking Change Minimum version of ReactiveSwift is now 5.0. #1817 by @larryonoff.
    • ๐Ÿ’ฅ Breaking Change Minimum version of Result is now 4.1. #1817 by @larryonoff.
    • ๐Ÿ’ฅ Breaking Change Updated project to Swift 5.0. #1827 by @sunshinejr.
    • โšก๏ธ Updated project to support Xcode 10.2. #1826 by @larsschwegmann.
    • MoyaError now conforms to CustomNSError protocol, makes underlying errors available in its user-info dictionary. #1783 by @dpoggi.

    ๐Ÿ›  Fixed

    • ๐Ÿ›  Fixed Progress object on responses that did not specify correct Content-Length header. Now, whenever there is no valid header, the progress will be 0.0 until the completion of the request. Also, the completed property is now true only when the response was serialized, we do not rely on progress being 1.0 anymore. #1815 by @sunshinejr.

    โœ‚ Removed

    • ๐Ÿ’ฅ Breaking change Removed validate on TargetType. It was deprecated in Moya 11, use validationType instead. #1828 by @sunshinejr.
  • v13.0.0-beta.1 Changes

    March 31, 2019

    ๐Ÿฑ Xcode 10.2, Swift 5.0 and more! ๐Ÿš€

    ๐Ÿ”„ Changed

    • ๐Ÿ’ฅ Breaking Change .mapImage() extension on Single and Observable now returns non-optional image. #1789, #1799 by @bjarkehs and @sunshinejr.
    • ๐Ÿ’ฅ Breaking Change Minimum version of ReactiveSwift is now 5.0. #1817 by @larryonoff.
    • ๐Ÿ’ฅ Breaking Change Minimum version of Result is now 4.1. #1817 by @larryonoff.
    • ๐Ÿ’ฅ Breaking Change Updated project to Swift 5.0. #1827 by @sunshinejr.
    • โšก๏ธ Updated project to support Xcode 10.2. #1826 by @larsschwegmann.
    • MoyaError now conforms to CustomNSError protocol, makes underlying errors available in its user-info dictionary. #1783 by @dpoggi.

    ๐Ÿ›  Fixed

    • ๐Ÿ›  Fixed Progress object on responses that did not specify correct Content-Length header. Now, whenever there is no valid header, the progress will be 0.0 until the completion of the request. Also, the completed property is now true only when the response was serialized, we do not rely on progress being 1.0 anymore. #1815 by @sunshinejr.

    โœ‚ Removed

    • ๐Ÿ’ฅ Breaking change Removed validate on TargetType. It was deprecated in Moya 11, use validationType instead. #1828 by @sunshinejr.
  • v12.0.1 Changes

    November 19, 2018

    ๐Ÿš€ This release fixes the installation issues for the Moya/RxSwift and Moya/ReactiveSwift subspecs via CocoaPods (#1768). Please use this as the minimum version for 12.x releases.

  • v12.0.0 Changes

    November 19, 2018

    ๐Ÿš€ This release is long overdue but Moya 12.0 is finally here! ๐ŸŽ‰ The latest version of Moya now supports Swift 4.2 as well as version 4.X of RxSwift and 4.X of ReactiveSwift. Additionally, we've made a highly requested addition to the AccessTokenPlugin - the ability to set a header token in a custom format ๐Ÿ‘

    ๐Ÿš€ Thanks to all the contributors to this release, @SeRG1k17, @sunshinejr, @SimonRice, @LucianoPAlmeida, @lexorus, as well as everyone else who makes this project possible โค๏ธ

    Full Changelog for Moya 12.0:

    โž• Added

    • ๐Ÿ’ฅ Breaking Change Added .custom(String) authorization case to AuthorizationType inside AccessTokenPlugin. #1611 by @SeRG1k17.

    ๐Ÿ”„ Changed

    ๐Ÿ’ฅ Breaking Change watchOS deployment target for RxMoya is now 3.0. #1758 by @simonrice.

    ๐Ÿ’ฅ Breaking Change Minimum version of ReactiveSwift is now 4.0. #1668 by @sunshinejr.

    ๐Ÿ’ฅ Breaking Change Minimum version of Result is now 4.0. #1668 by @sunshinejr.

    ๐Ÿ’ฅ Breaking Change Changed Responses filter method parameter to use a generic RangeExpression that accepts any range type. #1624 by @LucianoPAlmeida.

    ๐Ÿ’ฅ Breaking Change Changed AccessTokenPlugin's initializer to no longer use an @autoclosure for the tokenClosure parameter. #1611 by @SeRG1k17.

    ๐Ÿ›  Fixed

    • ๐Ÿ›  Fix warnings generated by Xcode 10. Updated project to Swift 4.2
      #1740 by @lexorus
  • v12.0.0-beta.1 Changes

    August 07, 2018

    โž• Added

    • ๐Ÿ’ฅ Breaking Change Added .custom(String) authorization case to AuthorizationType inside AccessTokenPlugin. #1611 by @SeRG1k17.

    ๐Ÿ”„ Changed

    ๐Ÿ’ฅ Breaking Change Minimum version of ReactiveSwift is now 4.0. #1668 by @sunshinejr.

    ๐Ÿ’ฅ Breaking Change Minimum version of Result is now 4.0. #1668 by @sunshinejr.

    ๐Ÿ’ฅ Breaking Change Changed Responses filter method parameter to use a generic RangeExpression that accepts any range type. #1624 by @LucianoPAlmeida.

    ๐Ÿ’ฅ Breaking Change Changed AccessTokenPlugin's initializer to no longer use an @autoclosure for the tokenClosure parameter. #1611 by @SeRG1k17.

  • v11.0.2 Changes

    April 01, 2018

    ๐Ÿš€ This release is a small patch to fix Moya's Carthage compatibility.

    ๐Ÿ›  Fixed

    • ๐Ÿ›  Fixed Carthage compatibility by disabling the SwiftLint build phase in release builds. #1619 by @Dschee.
  • v11.0.1 Changes

    February 26, 2018

    ๐Ÿš€ This release fixes a few bugs regarding Alamofire validation not being performed on requests.

    ๐Ÿ›  Fixed

    • ๐Ÿ›  Fixed Alamofire validation not being performed on .uploadMultipart requests.
      #1591 by @SD10.
    • ๐Ÿ›  Fixed Alamofire validation not being performed on stubbed requests.
      #1593 by @SD10.
  • v11.0.0 Changes

    February 07, 2018
    • No changes