Move CI to Xcode 13.2 (#117)

.circleci/config.yml

@@ -9,7 +9,7 @@ anchors:
   - &test_output_folder test_output
   - &default_executor
     macos:
-      xcode: "13.0.0"
+      xcode: "13.2.1"
 
 env:
   global:
@@ -29,7 +29,7 @@ commands:
       path:
         type: string
     steps:
-      - fetch-pod-specs # Fetch the podspec repo changes first to be sure to always get the latest pods
+      # - fetch-pod-specs # Fetch the podspec repo changes first to be sure to always get the latest pods
       - run:
           command: |
             cd <<parameters.path>>
@@ -56,7 +56,7 @@ commands:
           path: <<parameters.path>>
           test_output_folder: *test_output_folder
 
-  # We introduced two separate commands for projects and workspaces because we didnt find a generic and non-confusing way to introduce
+  # We introduced two separate commands for projects and workspaces because we didn't find a generic and non-confusing way to introduce
   # a condition to only pass either the project or the workspace environment argument to the fastlane scan
   test_project_and_store_results:
     description: "Builds and tests a project and then stores the results of the tests as artifacts and test results report"

CHANGELOG.md

@@ -1,3 +1,7 @@
+# 1.10.1
+
+- Xcode 13.2 compatibility
+
 # 1.10.0
 
 - Xcode 13.0 compatibility

Flow.xcodeproj/project.pbxproj

@@ -673,7 +673,7 @@
 				LD_RUNPATH_SEARCH_PATHS = "$(inherited) @executable_path/Frameworks @loader_path/Frameworks";
 				LIBRARY_SEARCH_PATHS = "$(inherited)";
 				MACOSX_DEPLOYMENT_TARGET = 10.11;
-				MARKETING_VERSION = 1.10;
+				MARKETING_VERSION = 1.10.1;
 				OTHER_SWIFT_FLAGS = "-Xfrontend -warn-long-function-bodies=300 -Xfrontend -warn-long-expression-type-checking=300";
 				PRODUCT_BUNDLE_IDENTIFIER = com.iZettle.Flow;
 				PRODUCT_NAME = "$(TARGET_NAME)";
@@ -701,7 +701,7 @@
 				LD_RUNPATH_SEARCH_PATHS = "$(inherited) @executable_path/Frameworks @loader_path/Frameworks";
 				LIBRARY_SEARCH_PATHS = "$(inherited)";
 				MACOSX_DEPLOYMENT_TARGET = 10.11;
-				MARKETING_VERSION = 1.10;
+				MARKETING_VERSION = 1.10.1;
 				OTHER_SWIFT_FLAGS = "-Xfrontend -warn-long-function-bodies=300 -Xfrontend -warn-long-expression-type-checking=300";
 				PRODUCT_BUNDLE_IDENTIFIER = com.iZettle.Flow;
 				PRODUCT_NAME = "$(TARGET_NAME)";

FlowFramework.podspec

@@ -1,6 +1,6 @@
 Pod::Spec.new do |s|
   s.name         = "FlowFramework"
-  s.version      = "1.10.0"
+  s.version      = "1.10.1"
   s.module_name  = "Flow"
   s.summary      = "Working with asynchronous flows"
   s.description  = <<-DESC

README.md

@@ -4,7 +4,7 @@
 [![Platforms](https://img.shields.io/badge/platform-%20iOS%20|%20macOS%20|%20tvOS%20|%20linux-gray.svg)](https://img.shields.io/badge/platform-%20iOS%20|%20macOS%20|%20tvOS%20|%20linux-gray.svg)
 [![Carthage Compatible](https://img.shields.io/badge/Carthage-compatible-4BC51D.svg?style=flat)](https://github.com/Carthage/Carthage)
 [![Swift Package Manager Compatible](https://img.shields.io/badge/SwiftPM-Compatible-brightgreen.svg)](https://github.com/apple/swift-package-manager)
-![Xcode version](https://img.shields.io/badge/Xcode-13.0.0-blue)
+![Xcode version](https://img.shields.io/badge/Xcode-13.2.0-green)
 
 Modern applications often contain complex asynchronous flows and life cycles. Flow is a Swift library aiming to simplify building these by solving three main problems: