rake-protect 1.0.0 → 1.0.1

Sign up to get free protection for your applications and to get access to all the features.
Files changed (3) hide show
  1. checksums.yaml +4 -4
  2. data/README.md +3 -2
  3. metadata +3 -3
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA1:
3
- metadata.gz: 45b92ba09a39bf90ff416eae9dd63ab44e149e91
4
- data.tar.gz: 4f873e1292850b503b7ebfe8e5f463632ae49972
3
+ metadata.gz: ae0099994ed9bdad5ebbc3ce1475f088af9d258c
4
+ data.tar.gz: 60e0d5bad14a7b3bdd91a15e6e57d20f72a132e2
5
5
  SHA512:
6
- metadata.gz: 7df4c00f6d40611d834ee603952810ac091826bfad6101c33de2ab95b091b52f1a725f3b4024114d7068e1938c66f7b9de83d90d4d99e4b8bee748c28bfc4ecd
7
- data.tar.gz: 6bd4cd8183034d97627de9dc7f6630dd9d177ae18d9f33247c8b3c171733812c0bf43a6b07f36d1ddfc35eff3d84fa2d70274ea46b49ba1193fffbef37bc712a
6
+ metadata.gz: 89041394ad77d99319ed250db63bfb73cbfe984c737740bec746c9b8ffcf6590aadfc90b8d3d3261ba703b71b3509369e398cf8d5d146aa3958d1d387092f0ba
7
+ data.tar.gz: 8fe468a28e8e5e29a6660d1b267f671f62c95943e302a06721440a48a78e69670f9e775390e7d510f1d2e452b43ac65930f89f63d0f5b3150e50bbd5987c9bcc
data/README.md CHANGED
@@ -1,7 +1,8 @@
1
1
  # rake-protect
2
2
 
3
- [![build status](https://gitlab.com/mtuchowski/rake-protect/badges/master/build.svg)](https://gitlab.com/mtuchowski/rake-protect/commits/master)
4
- [![coverage report](https://gitlab.com/mtuchowski/rake-protect/badges/master/coverage.svg)](https://gitlab.com/mtuchowski/rake-protect/commits/master)
3
+ [![Build Status](https://gitlab.com/mtuchowski/rake-protect/badges/master/build.svg)](https://gitlab.com/mtuchowski/rake-protect/commits/master)
4
+ [![Coverage Report](https://gitlab.com/mtuchowski/rake-protect/badges/master/coverage.svg)](https://gitlab.com/mtuchowski/rake-protect/commits/master)
5
+ [![Gem Version](https://badge.fury.io/rb/rake-protect.svg)](https://badge.fury.io/rb/rake-protect)
5
6
 
6
7
  When some gems are unavailable in an environment, for example on a production server, requiring them in a `Rakefile` will cause `LoadError` to be thrown. Wrap the require and task declaration in `Rake.protect` block to prevent that.
7
8
 
metadata CHANGED
@@ -1,7 +1,7 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: rake-protect
3
3
  version: !ruby/object:Gem::Version
4
- version: 1.0.0
4
+ version: 1.0.1
5
5
  platform: ruby
6
6
  authors:
7
7
  - Marek Tuchowski
@@ -208,8 +208,8 @@ dependencies:
208
208
  version: '0.2'
209
209
  description: |2
210
210
  When some gems are unavailable in an environment, for example on a production server, requiring
211
- them in a `Rakefile` will cause `LoadError` to be thrown. Wrap the require and task declaration
212
- in `Rake.protect` block to prevent that.
211
+ them in a Rakefile will cause LoadError to be thrown. Wrap the require and task declaration
212
+ in Rake.protect block to prevent that.
213
213
  email: marek@tuchowski.com.pl
214
214
  executables: []
215
215
  extensions: []