coverband 4.2.0.rc3 → 4.2.0

Sign up to get free protection for your applications and to get access to all the features.
Files changed (4) hide show
  1. checksums.yaml +4 -4
  2. data/changes.md +10 -6
  3. data/lib/coverband/version.rb +1 -1
  4. metadata +4 -4
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: ec0eef95d0010eb453106f456601929b1ca7fec395f3edeee579d5652fb9dee5
4
- data.tar.gz: 8c17307ac929729630b8a550549d31ff48ae5f7da7cfa8ed63b9be8a7f597cb0
3
+ metadata.gz: 1e214b1bd6119046657daa64ed6d69f77f821c6c670b72e98d307ede5f08e61f
4
+ data.tar.gz: 469d9470799f90b5b52d53d3a630fae75b3b6bff0390375987902331878f530e
5
5
  SHA512:
6
- metadata.gz: 2ac7310ed234e195b9615d3a9852008cdbe6039c42ad0ea681d138406e8910dce3d5d58f582d9ea72f65d6f411af67b451c2513d8929b541e55df8df815bbdaa
7
- data.tar.gz: 62809588499c3ba212fd2e861fca0aaa2e6b4f0c451527b75346a688efb504b0be1393c5282e658bf338fc6770fd1b1714b390ede270c55dde44abff9ff7dc35
6
+ metadata.gz: f1b0f503941ab9dbc2dee6a184fe6d6d937a5f505a5c9112ae7343197372586d6cb42df758f24effde0ee30fb359c0e2e651c64a1f5ee4c9a588a4499683dc73
7
+ data.tar.gz: ee700abfe4c730011dcc5c1c8521f55a2cc7ec5149e44b08187c8d09419023160a0f7c8aaba4b2aa0bb405eb13f4aeee1d8ce9cabce4860738d4ea94cac63c04
data/changes.md CHANGED
@@ -73,9 +73,16 @@ Feature Ideas:
73
73
 
74
74
  # Alpha
75
75
 
76
- ### Coverband 4.2.0.rc
76
+ ### Coverband 4.3.0?
77
77
 
78
- For this release your combined coverage is OK, but your runtime coverage will be incorrect until you reset your coverage. This is due to an additive change in how we store coverage. We didn't reset by default as the coverage history for some folks may be more important than runtime breakdown.
78
+ - further improvements on eager_loading detection
79
+ - ?
80
+
81
+ # Released
82
+
83
+ ### Coverband 4.2.0
84
+
85
+ **NOTE:** This release introduces load time and runtime Coverage. To get the full benifit of this feature you need to reset you coverage data (`rake coverband:clear` or clear via the web UI). Until you clear the combined result is still correct, but your runtime data will be mixed with previous data. This is due to an additive change in how we store coverage. We didn't reset by default as the coverage history for some folks may be more important than runtime breakdown.
79
86
 
80
87
  - loadtime vs runtime coverage
81
88
  - This fixes the coverage last seen date to exclude just load time data
@@ -89,10 +96,7 @@ For this release your combined coverage is OK, but your runtime coverage will be
89
96
  - move from thread based reporter instance to process based instance
90
97
  - thanks Karl Baum for much of the above mentioned work
91
98
  - clear coverage on individual files
92
-
93
- # Released
94
-
95
- ### Coverband 4.2.0
99
+ - we have a logo, thanks Dave Woodall
96
100
 
97
101
  ### Coverband 4.1.1
98
102
 
@@ -1,5 +1,5 @@
1
1
  # frozen_string_literal: true
2
2
 
3
3
  module Coverband
4
- VERSION = '4.2.0.rc3'
4
+ VERSION = '4.2.0'
5
5
  end
metadata CHANGED
@@ -1,7 +1,7 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: coverband
3
3
  version: !ruby/object:Gem::Version
4
- version: 4.2.0.rc3
4
+ version: 4.2.0
5
5
  platform: ruby
6
6
  authors:
7
7
  - Dan Mayer
@@ -9,7 +9,7 @@ authors:
9
9
  autorequire:
10
10
  bindir: bin
11
11
  cert_chain: []
12
- date: 2019-04-23 00:00:00.000000000 Z
12
+ date: 2019-04-24 00:00:00.000000000 Z
13
13
  dependencies:
14
14
  - !ruby/object:Gem::Dependency
15
15
  name: aws-sdk-s3
@@ -404,9 +404,9 @@ required_ruby_version: !ruby/object:Gem::Requirement
404
404
  version: '0'
405
405
  required_rubygems_version: !ruby/object:Gem::Requirement
406
406
  requirements:
407
- - - ">"
407
+ - - ">="
408
408
  - !ruby/object:Gem::Version
409
- version: 1.3.1
409
+ version: '0'
410
410
  requirements: []
411
411
  rubyforge_project:
412
412
  rubygems_version: 2.7.8