Updates swift version

Author: Sven Jansen

CellularRemoteConfiguration.podspec

@@ -1,6 +1,6 @@
 Pod::Spec.new do |spec|
     spec.version       = '8.0.1'
-    spec.swift_version = '5.6.1'
+    spec.swift_version = '5.6.0'
     spec.module_name   = 'RemoteConfiguration'
     spec.name          = 'CellularRemoteConfiguration'
     spec.summary       = 'Dynamic configuration of iOS, tvOS or watchOS application using remote files.'

Package.swift

@@ -1,4 +1,4 @@
-// swift-tools-version:5.1
+// swift-tools-version:5.6.0
 import PackageDescription
 
 let package = Package(
@@ -16,7 +16,10 @@ let package = Package(
         .package(url: "https://github.com/cellular/localstorage-swift.git", from: "6.0.0")
     ],
     targets: [
-        .target(name: "RemoteConfiguration", dependencies: ["CELLULAR", "LocalStorage"]),
+        .target(name: "RemoteConfiguration", dependencies: [
+            .product(name: "CELLULAR", package: "cellular-swift"),
+            .product(name: "LocalStorage", package: "localstorage-swift")
+        ]),
         .testTarget(name: "RemoteConfigurationTests", dependencies: ["RemoteConfiguration"]),
     ]
 )

README.md

@@ -153,7 +153,7 @@ The dependency to CellularNetworking has been removed in this version.
 The adapter to bind RemoteConfiguration to CellularNetworking has been moved to ```Example/Example/Controller/RemoteConfiguration+Adapter.swift```. This adapter must be copied to the Application to bind RemoteConfiguration to CellularNetworking or any other networking clients like Alamofire or plain NSURLSession.
 
 
-## Update for version 8.0.0
+## Update for version 8.0.1
 
 For mandatory updates it's now possible to ignore one or more iOS versions. iOS Versions contained in the array of "ignoredOSVersions" will not react to mandatory updates until the version is removed from the array. 
 This could be useful if you don't support special iOS versions anymore but the last working version should stil exist on the AppStore and should not be disabled by a mandatory update. If there is a breaking API change later on, you still have the ability to remove this version from the list and the mandatory update will be shown as usual.