opskeleton 0.4.4 → 0.4.5

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 9b52de7c4675f155af2b31a093aa253fe7179469
-  data.tar.gz: 1ed1a417000ba6050068fb1051e3f17b51088644
+  metadata.gz: fb8e6cfdc4545ead41ce026add622d10a3c6b7e6
+  data.tar.gz: 142bf7f79131d930062982a2d317eb7eac8d4f09
 SHA512:
-  metadata.gz: 62dabb7d933a806f5ca713f6f32482708ade4f012a3416e955c30987cfe7c952a56f753c05e8a306a259ff4901265ffd2bb72bf6cda0f108f0168846b3498a3e
-  data.tar.gz: ef9158f66fff15787c46d188bb442e0a8ea8495cab9560e962e23ad1400fd2fa18615c087d01c140477dd342c3bc06763aa321552706233b7074d67da1cba268
+  metadata.gz: a691af74c57934132d1339f4de8074326fd242ed7cc7085da211180f738f3ce79b23f54bed9249617ff74e726b994a93512c01f3117e00cdffdfb7e9a3a8c4e5
+  data.tar.gz: 7e484c8928869d46bf0a1c6e062eaf8507d857a95f731a3542f454f593a96b44b52fa757af15bdb1a8eb86fb1c88b71be4fc975288643416ea3166a9c93e5fa3

data/Gemfile.lock

@@ -1,14 +1,14 @@
 PATH
   remote: .
   specs:
-    opskeleton (0.4.3)
+    opskeleton (0.4.4)
       bintray_deploy
       thor
 
 GEM
   remote: https://rubygems.org/
   specs:
-    bintray_deploy (0.0.3)
+    bintray_deploy (0.0.4)
       configuration
       rest-client
       thor

data/README.md

@@ -106,6 +106,7 @@ The packaged tar files can be consumed using any tool and protocol however http
 ```bash 
 $ opsk package
 $ opsk deploy <bintray-repo>
+deployed foo-sandbox-0.0.1.tar.gz to http://dl.bintray.com/narkisr/<bintray-repo>/foo-sandbox-0.0.1.tar.gz
 ```
 
 Make sure to  [configure](https://github.com/narkisr/bintray-deploy#usage) configure the bintray API key.

data/lib/opskeleton/version.rb

@@ -1,3 +1,3 @@
 module Opskeleton
-  VERSION = '0.4.4'
+  VERSION = '0.4.5'
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: opskeleton
 version: !ruby/object:Gem::Version
-  version: 0.4.4
+  version: 0.4.5
 platform: ruby
 authors:
 - narkisr