strong_versions 0.3.1 → 0.3.2
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/Makefile +3 -3
- data/README.md +5 -3
- data/doc/images/ci-pipeline.png +0 -0
- data/doc/images/strong-versions-example.png +0 -0
- data/lib/strong_versions/dependency.rb +4 -3
- data/lib/strong_versions/terminal.rb +1 -1
- data/lib/strong_versions/version.rb +1 -1
- metadata +3 -2
checksums.yaml
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
SHA256:
|
|
3
|
-
metadata.gz:
|
|
4
|
-
data.tar.gz:
|
|
3
|
+
metadata.gz: 9589edc74d736ee2c17217c9bf8c4efe316c8ada4842ecec28a16d27f939afa9
|
|
4
|
+
data.tar.gz: 438bcc252b6bde7667b223b2efd55f26ca56597b21f5f238b9747ad78b1fb96b
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: 1688a28f9c4c9fa03c78c99d59994508bfa1cec61005751aa2e0b32f5388cec5736557449ae072965ef6448c229e4527bcbee7f53581e2cf47fbf8df72ea8e2f
|
|
7
|
+
data.tar.gz: aeae4848ecfb0ad258806e42ca4294d5010d0c7cbf5c434914eea8dc29214f1e9c7be11cd1c6c5de0c37683f2efad5ba88a110038ef84415566ed365970697d3
|
data/Makefile
CHANGED
data/README.md
CHANGED
|
@@ -28,7 +28,7 @@ The benefit of applying this standard is that, if all gems follow [Semantic Vers
|
|
|
28
28
|
Add the gem to your `Gemfile`
|
|
29
29
|
|
|
30
30
|
```ruby
|
|
31
|
-
gem 'strong_versions', '~> 0.3.
|
|
31
|
+
gem 'strong_versions', '~> 0.3.2'
|
|
32
32
|
```
|
|
33
33
|
|
|
34
34
|
And rebuild your bundle:
|
|
@@ -39,7 +39,7 @@ $ bundle install
|
|
|
39
39
|
|
|
40
40
|
Or install yourself:
|
|
41
41
|
```bash
|
|
42
|
-
$ gem install strong_versions -v '0.3.
|
|
42
|
+
$ gem install strong_versions -v '0.3.2'
|
|
43
43
|
```
|
|
44
44
|
|
|
45
45
|
## Usage
|
|
@@ -50,7 +50,9 @@ _StrongVersions_ is invoked with a provided executable:
|
|
|
50
50
|
$ bundle exec strong_versions
|
|
51
51
|
```
|
|
52
52
|
|
|
53
|
-
The executable will output all non-passing gems and will return an exit code of `1` on failure, `0` on success (i.e. all gems passing).
|
|
53
|
+
The executable will output all non-passing gems and will return an exit code of `1` on failure, `0` on success (i.e. all gems passing). This makes _StrongVersions_ suitable for use in a continuous integration pipeline:
|
|
54
|
+
|
|
55
|
+
|
|
54
56
|
|
|
55
57
|
### Exclusions
|
|
56
58
|
|
|
Binary file
|
|
Binary file
|
|
@@ -41,9 +41,10 @@ module StrongVersions
|
|
|
41
41
|
end
|
|
42
42
|
|
|
43
43
|
def lockfile_version
|
|
44
|
-
@lockfile_version ||=
|
|
45
|
-
@lockfile.specs.find { |spec| spec.name == @name }
|
|
46
|
-
|
|
44
|
+
@lockfile_version ||= begin
|
|
45
|
+
gem_spec = @lockfile.specs.find { |spec| spec.name == @name }
|
|
46
|
+
gem_spec.nil? ? nil : version(gem_spec.version)
|
|
47
|
+
end
|
|
47
48
|
end
|
|
48
49
|
|
|
49
50
|
def default_lockfile
|
|
@@ -37,7 +37,7 @@ module StrongVersions
|
|
|
37
37
|
# Success and failure output format brazenly stolen from Rubocop.
|
|
38
38
|
def success(count)
|
|
39
39
|
color(
|
|
40
|
-
"#{count} #{t('checked')}, %{no_issues} #{t('detected')}",
|
|
40
|
+
"#{count} #{t('checked')}, %{no_issues} #{t('detected')}\n",
|
|
41
41
|
:default,
|
|
42
42
|
no_issues: [t('no_issues'), :green]
|
|
43
43
|
)
|
metadata
CHANGED
|
@@ -1,14 +1,14 @@
|
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
|
2
2
|
name: strong_versions
|
|
3
3
|
version: !ruby/object:Gem::Version
|
|
4
|
-
version: 0.3.
|
|
4
|
+
version: 0.3.2
|
|
5
5
|
platform: ruby
|
|
6
6
|
authors:
|
|
7
7
|
- Bob Farrell
|
|
8
8
|
autorequire:
|
|
9
9
|
bindir: bin
|
|
10
10
|
cert_chain: []
|
|
11
|
-
date: 2018-12-
|
|
11
|
+
date: 2018-12-25 00:00:00.000000000 Z
|
|
12
12
|
dependencies:
|
|
13
13
|
- !ruby/object:Gem::Dependency
|
|
14
14
|
name: i18n
|
|
@@ -162,6 +162,7 @@ files:
|
|
|
162
162
|
- bin/setup
|
|
163
163
|
- bin/strong_versions
|
|
164
164
|
- config/locales/en.yml
|
|
165
|
+
- doc/images/ci-pipeline.png
|
|
165
166
|
- doc/images/strong-versions-example.png
|
|
166
167
|
- lib/strong_versions.rb
|
|
167
168
|
- lib/strong_versions/config.rb
|