cocoapods-keys 2.0.6 → 2.0.7

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: bc0f07f741031ac24b6d2450cfa07b82c4732e393a988738d2b2ae67c6cd5922
-  data.tar.gz: ff941516ab6ee39a0a0d0bbd8fe02c4562aa83c3eb8f1a0ac00fa092b290d641
+  metadata.gz: d212c192545c118db8780995809a10adf90973c52eb10672a09f0b3bdc82aaf8
+  data.tar.gz: cc3c43a86c1dfc8dae80a2c07a707b6b632129503b86c38d0e70144e3bb315d7
 SHA512:
-  metadata.gz: 2d47f69d423d3aadd7b1a85c0ba65f42eaa238e45ea7aea2004a14e9a4c08d3e555276a2342cfb47d1de1298a5f6be86599ae90711737704b998b2438ea93f40
-  data.tar.gz: 5d9b55f10b0c6c5a47d340a7cd80e0e9d897e2ffb5dcb53beada8a1c80bf253f2f1ef49d424cb5458de98cff08808b7a66cb86ddd4476eda1ff20c469a071090
+  metadata.gz: b344a3a7f80c9d5eda7e16abd3463ff136a2ed56565846e83f366eea71e3b30395d7ec0c452320b00d7e1bff16da03a2e9d20a1edd3e112eb1b5187c861d51c3
+  data.tar.gz: db05659e7d4796bd55be7aa0c25f6335b0cc90a4400c55fa6767ad451768ac8b0090b27e9f29ca10bbaa0b3c712fc1af03ff9db71865c9c6b78da1fa73a0465e

data/CHANGELOG.md

@@ -1,5 +1,13 @@
 ## Master
 
+## 2.0.7
+
+* Fix keys not recorded in YML on first run. [ileitch]
+
+## 2.0.6
+
+* Makes list of keys unique on the yaml file [leoformaggio]
+
 ## 2.0.4 - 2.0.5
 
 * Handles more CIs [SlaunchaMan]
@@ -10,15 +18,15 @@
 
 ## 2.0.2
 
-* Sets a minimum iOS target of 8.0 [orta] 
+* Sets a minimum iOS target of 8.0 [orta]
 
 ## 2.0.1
 
-* Handles more CI types [m-ruhl] 
+* Handles more CI types [m-ruhl]
 
 ## 2.0.0
 
-* Handles casing correctly in generated key names [breaking] [marcelofabri] 
+* Handles casing correctly in generated key names [breaking] [marcelofabri]
 * Adds Nullability notations to default erb template [Skogetroll]
 * Use properties for accessing key values instead of functions [breaking, for swift] [Skogetroll]
 * Don't ask for keys on the command line when running on CI. [dantoml]

data/Gemfile.lock

@@ -1,7 +1,7 @@
 PATH
   remote: .
   specs:
-    cocoapods-keys (2.0.6)
+    cocoapods-keys (2.0.7)
       dotenv
       osx_keychain
 

data/README.md

@@ -42,23 +42,23 @@ Then running `pod install` will prompt for the keys not yet set and you can ensu
 
 You can save keys on a per-project basis by running the command:
 
-    $ pod keys set KEY VALUE
+    $ bundle exec pod keys set KEY VALUE
 
 You can list all known keys by running:
 
-    $ pod keys
+    $ bundle exec pod keys
 
 For example:
 
 ``` sh
   $ cd MyApplication
-  $ pod keys set "NetworkAPIToken" "AH2ZMiraGQbyUd9GkNTNfWEdxlwXcmHciEOH"
+  $ bundle exec pod keys set "NetworkAPIToken" "AH2ZMiraGQbyUd9GkNTNfWEdxlwXcmHciEOH"
   Saved NetworkAPIToken to MyApplication.
 
-  $ pod keys set "AnalyticsToken" "6TYKGVCn7sBSBFpwfSUCclzDoSBtEXw7"
+  $ bundle exec pod keys set "AnalyticsToken" "6TYKGVCn7sBSBFpwfSUCclzDoSBtEXw7"
   Saved AnalyticsToken to MyApplication.
 
-  $ pod keys
+  $ bundle exec pod keys
   Keys for MyApplication
    ├  NetworkAPIToken - AH2ZMiraGQbyUd9GkNTNfWEdxlwXcmHciEOH
    └  AnalyticsToken - 6TYKGVCn7sBSBFpwfSUCclzDoSBtEXw7
@@ -95,16 +95,16 @@ Some documentation is also available to [use cocoapods-keys in Swift projects](S
 
 CocoaPods-keys has 3 other commands:
 
- * `pod keys get [key] [optional project]`
+ * `bundle exec pod keys get [key] [optional project]`
    Which will output the value of the key to STDOUT, useful for scripting.
 
- * `pod keys rm [key] [optional project]`
-   Will remove a key from a project.  
+ * `bundle exec pod keys rm [key] [optional project]`
+   Will remove a key from a project.
 
-   If Wildcards are included, it will remove the keys matching the pattern. E.g.: `pod keys rm "G*og*"` will remove *all* the keys that begin with 'G', have 'og' in the middle and end with anything.  
-	To nuke all the keys, run either `pod keys rm "*"` or `pod keys rm --all`
+   If Wildcards are included, it will remove the keys matching the pattern. E.g.: `bundle exec pod keys rm "G*og*"` will remove *all* the keys that begin with 'G', have 'og' in the middle and end with anything.
+	To nuke all the keys, run either `bundle exec pod keys rm "*"` or `bundle exec pod keys rm --all`
 
- * `pod keys generate [optional project]`
+ * `bundle exec pod keys generate [optional project]`
    Will generate the obfuscated Objective-C keys class (mainly used internally).
 
 #### Continuous Integration

data/SWIFT_PROJECTS.md

@@ -1,7 +1,7 @@
 # Using CocoaPods-Keys in Swift projects
 
 Once you've followed the setup instructions described in the [Usage](README.md#usage)
-section of the README, you have two choices.
+section of the README, you are ready to use `Keys` from Swift.
 
 ## Importing the framework
 

data/lib/cocoapods_keys.rb

@@ -1,3 +1,3 @@
 module CocoaPodsKeys
-  VERSION = '2.0.6'.freeze
+  VERSION = '2.0.7'.freeze
 end

data/lib/preinstaller.rb

@@ -65,7 +65,6 @@ module CocoaPodsKeys
           setter.run
         end
       end
-      CocoaPodsKeys::KeyringLiberator.save_keyring(keyring)
 
       existing_keyring || !keys.empty?
     end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: cocoapods-keys
 version: !ruby/object:Gem::Version
-  version: 2.0.6
+  version: 2.0.7
 platform: ruby
 authors:
 - Orta Therox
@@ -9,7 +9,7 @@ authors:
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2018-10-19 00:00:00.000000000 Z
+date: 2019-01-04 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: osx_keychain