Alamofire v4.0.0-beta.1 Release Notes

  • ๐Ÿš€ Released on 2016-08-28. All issues associated with this milestone can be found using this filter.

    โž• Added

    • discardableResult annotations to all top-level Request APIs.

    โšก๏ธ Updated

    • โœ… All source, test and example logic as well as project settings to compile against the Xcode 8 beta releases.
    • ๐Ÿš€ Deployment targets to iOS 9.0, macOS 10.11, tvOS 9.0 and watchOS 2.0.
    • Notifications to use nested structs inside Notification.Name namespace.
    • The Manager class to SessionManager to be more descriptive.
    • The SessionDelegate, TaskDelegate and subclasses by pulling them into the global namespace.
    • ๐Ÿ“š All the Core APIs and documentation to match Swift 3 API design guidelines.
    • The SessionDelegate to store Request instances internally to prepare for retry logic.
    • ๐Ÿš€ The podspec to 4.0.0-beta.1 and bumped the deployment targets.
    • The parameter order of custom URLRequest initializer to match other APIs.
    • The travis yaml file for Xcode 8.
    • The Error enum to AFError which now conforms to the new Error protocol.

    ๐Ÿ›  Fixed

    • ๐Ÿ”จ Typo in a parameter name in the MultipartFormData Swift 3 API refactor.

    โฌ†๏ธ Upgrade Notes

    This release requires Xcode 8.0 beta 6+ because it has been completely refactored to compile against Swift 3.0. Any older versions of Xcode will NOT COMPILE.

    This release is the start of the Alamofire 4.0.0 beta releases. We still have quite a few large changes we're trying to squeeze in before the Xcode 8 GM drops, so the APIs will continue to change over the next few weeks. Please keep in mind that each beta will likely bring new APIs and also refactor others. The betas WILL NOT follow semantic versioning. We'll most likely conform to semantic versioning once we start releasing the RCs unless we run into a major unforeseen issue.

    ๐Ÿš€ We'd really appreciate everyone trying out the betas and letting us know if you find issues. We want to address every possible issue prior to the official Alamofire 4.0.0 release.