keybase-core 0.1.4 → 0.1.7
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- checksums.yaml +4 -4
- checksums.yaml.gz.sig +0 -0
- data.tar.gz.sig +0 -0
- data/Gemfile.lock +4 -4
- data/README.md +2 -2
- data/keybase-core.gemspec +3 -3
- data/releasing.md +9 -0
- metadata +5 -4
- metadata.gz.sig +0 -0
checksums.yaml
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
SHA1:
|
|
3
|
-
metadata.gz:
|
|
4
|
-
data.tar.gz:
|
|
3
|
+
metadata.gz: 8a05b5fe1fd905941ebf4f45e1d9cb281c273248
|
|
4
|
+
data.tar.gz: 2d86e1d6a59515e5917063cec1af252bca2e40ea
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: 10815c0254084dfc264b1095c038112cd0679420a4f392cd47825aa82265ccdf712b4e9559e33d33981a536a90e945684f6f1b20df334cf4048f4949f7757029
|
|
7
|
+
data.tar.gz: 9794baed1fcc92ca0682aa96d7dd6523d832db24b1678f48cbbcd0c9981c02ad50cdb68af98da1a179c30af25506c36ee65f1865e6cf6f87a68ead6b2f9ce2da
|
checksums.yaml.gz.sig
CHANGED
|
Binary file
|
data.tar.gz.sig
CHANGED
|
Binary file
|
data/Gemfile.lock
CHANGED
|
@@ -1,8 +1,8 @@
|
|
|
1
1
|
PATH
|
|
2
2
|
remote: .
|
|
3
3
|
specs:
|
|
4
|
-
keybase-core (0.1.
|
|
5
|
-
faraday (~> 0.9.
|
|
4
|
+
keybase-core (0.1.7)
|
|
5
|
+
faraday (~> 0.9.1)
|
|
6
6
|
scrypt (~> 2.0.0)
|
|
7
7
|
|
|
8
8
|
GEM
|
|
@@ -18,7 +18,7 @@ GEM
|
|
|
18
18
|
crack (0.4.2)
|
|
19
19
|
safe_yaml (~> 1.0.0)
|
|
20
20
|
docile (1.1.3)
|
|
21
|
-
faraday (0.9.
|
|
21
|
+
faraday (0.9.1)
|
|
22
22
|
multipart-post (>= 1.2, < 3)
|
|
23
23
|
ffi (1.9.6)
|
|
24
24
|
ffi-compiler (0.1.3)
|
|
@@ -28,7 +28,7 @@ GEM
|
|
|
28
28
|
minitest (5.3.1)
|
|
29
29
|
multi_json (1.9.2)
|
|
30
30
|
multipart-post (2.0.0)
|
|
31
|
-
rake (10.
|
|
31
|
+
rake (10.4.2)
|
|
32
32
|
rest-client (1.6.7)
|
|
33
33
|
mime-types (>= 1.16)
|
|
34
34
|
safe_yaml (1.0.1)
|
data/README.md
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|

|
|
2
2
|
|
|
3
|
-
Gem wrapper for [keybase.io](https://keybase.io) core API
|
|
3
|
+
Gem wrapper for [keybase.io](https://keybase.io) core API.
|
|
4
4
|
|
|
5
5
|
[] (http://travis-ci.org/keybase/ruby-core) [](http://badge.fury.io/rb/keybase-core) [](https://gemnasium.com/seanhandley/ruby-core) [](https://coveralls.io/r/seanhandley/ruby-core?branch=master) [](https://codeclimate.com/github/keybase/ruby-core)
|
|
6
6
|
|
|
@@ -38,7 +38,7 @@ Upon login, you'll get back a user object. Your user object is essentially a lar
|
|
|
38
38
|
The login will also initiate an ongoing session which allows the authenticated actions: `key/add`, `key/revoke`, `sig/post_auth`
|
|
39
39
|
|
|
40
40
|
```ruby
|
|
41
|
-
me = Keybase::Core.login('chris', 'passphrase')
|
|
41
|
+
me = Keybase::Core::User.login('chris', 'passphrase')
|
|
42
42
|
me.basics.username #=> "chris"
|
|
43
43
|
me.private_keys.primary.kid #=> "a140c70404a13370f7..."
|
|
44
44
|
```
|
data/keybase-core.gemspec
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
Gem::Specification.new do |gem|
|
|
2
2
|
gem.name = 'keybase-core'
|
|
3
|
-
gem.version = '0.1.
|
|
4
|
-
gem.date = '
|
|
3
|
+
gem.version = '0.1.7'
|
|
4
|
+
gem.date = '2015-02-24'
|
|
5
5
|
gem.summary = 'keybase-core'
|
|
6
6
|
gem.description = 'Core Ruby lib for keybase.io'
|
|
7
7
|
gem.authors = [ 'Max Krohn', 'Sean Handley' ]
|
|
@@ -14,7 +14,7 @@ Gem::Specification.new do |gem|
|
|
|
14
14
|
|
|
15
15
|
# Runtime Dependencies
|
|
16
16
|
gem.add_runtime_dependency 'scrypt', '~> 2.0.0'
|
|
17
|
-
gem.add_runtime_dependency 'faraday', '~> 0.9.
|
|
17
|
+
gem.add_runtime_dependency 'faraday', '~> 0.9.1'
|
|
18
18
|
|
|
19
19
|
# Development Dependencies
|
|
20
20
|
gem.add_development_dependency 'vcr', '~> 2.8.0'
|
data/releasing.md
ADDED
|
@@ -0,0 +1,9 @@
|
|
|
1
|
+
* Update version number and date in .gemspec
|
|
2
|
+
* Run bundler to update Gemfile.lock with the new updated dependency for the gem (don't ask why it requires itself)
|
|
3
|
+
* Push to master
|
|
4
|
+
* Ensure travis tests are passing
|
|
5
|
+
* Create and push a new tag for the release
|
|
6
|
+
* Run `gem build keybase-core.gemspec` and auth with pass phrase
|
|
7
|
+
* Ensure it installs with `gem install keybase-xxx.gem -P HighSecurity`
|
|
8
|
+
* Create a release in Github's tags and attach the .gem file to the release.
|
|
9
|
+
* Finally, run `rake release` to push the new version to RubyGems
|
metadata
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
|
2
2
|
name: keybase-core
|
|
3
3
|
version: !ruby/object:Gem::Version
|
|
4
|
-
version: 0.1.
|
|
4
|
+
version: 0.1.7
|
|
5
5
|
platform: ruby
|
|
6
6
|
authors:
|
|
7
7
|
- Max Krohn
|
|
@@ -31,7 +31,7 @@ cert_chain:
|
|
|
31
31
|
5vYyMKBp8sXR+QZc4U1ho78vyyA02njxn+qub9oG9x5j+C+IdbFyyn78wChQ/YZA
|
|
32
32
|
t9QfTw+WVknE8zEJI5EFtpDk1aGaIKJ4WhzdnWRmIwad9Y60
|
|
33
33
|
-----END CERTIFICATE-----
|
|
34
|
-
date:
|
|
34
|
+
date: 2015-02-24 00:00:00.000000000 Z
|
|
35
35
|
dependencies:
|
|
36
36
|
- !ruby/object:Gem::Dependency
|
|
37
37
|
name: scrypt
|
|
@@ -53,14 +53,14 @@ dependencies:
|
|
|
53
53
|
requirements:
|
|
54
54
|
- - "~>"
|
|
55
55
|
- !ruby/object:Gem::Version
|
|
56
|
-
version: 0.9.
|
|
56
|
+
version: 0.9.1
|
|
57
57
|
type: :runtime
|
|
58
58
|
prerelease: false
|
|
59
59
|
version_requirements: !ruby/object:Gem::Requirement
|
|
60
60
|
requirements:
|
|
61
61
|
- - "~>"
|
|
62
62
|
- !ruby/object:Gem::Version
|
|
63
|
-
version: 0.9.
|
|
63
|
+
version: 0.9.1
|
|
64
64
|
- !ruby/object:Gem::Dependency
|
|
65
65
|
name: vcr
|
|
66
66
|
requirement: !ruby/object:Gem::Requirement
|
|
@@ -178,6 +178,7 @@ files:
|
|
|
178
178
|
- lib/keybase-core/request/user/lookup.rb
|
|
179
179
|
- lib/keybase-core/response.rb
|
|
180
180
|
- lib/keybase-core/token_store.rb
|
|
181
|
+
- releasing.md
|
|
181
182
|
- test/all.rb
|
|
182
183
|
- test/fixtures/example_dump.json
|
|
183
184
|
- test/fixtures/example_user.json
|
metadata.gz.sig
CHANGED
|
Binary file
|