Closed greenkeeper[bot] closed 6 years ago
Merging #53 into master will decrease coverage by
0.5%
. The diff coverage isn/a
.
@@ Coverage Diff @@
## master #53 +/- ##
==========================================
- Coverage 90.37% 89.86% -0.51%
==========================================
Files 4 4
Lines 187 227 +40
Branches 22 28 +6
==========================================
+ Hits 169 204 +35
Misses 6 6
- Partials 12 17 +5
Impacted Files | Coverage Ξ | |
---|---|---|
...rojects/lvo/logging/src/lib/log-manager.service.ts | 87.2% <0%> (-4.69%) |
:arrow_down: |
projects/lvo/logging/src/lib/log-level.enum.ts | 100% <0%> (ΓΈ) |
:arrow_up: |
projects/lvo/logging/src/test.ts | 100% <0%> (ΓΈ) |
:arrow_up: |
projects/lvo/logging/src/lib/logger.service.ts | 90.08% <0%> (+2.58%) |
:arrow_up: |
Continue to review full report at Codecov.
Legend - Click here to learn more
Ξ = absolute <relative> (impact)
,ΓΈ = not affected
,? = missing data
Powered by Codecov. Last update 63325af...72e1960. Read the comment docs.
devDependency
@angular-devkit/build-angular was updated from 0.6.8
to 0.8.2
.devDependency
@angular-devkit/build-angular was updated from 0.6.8
to 0.8.3
.devDependency
@angular-devkit/build-angular was updated from 0.6.8
to 0.8.4
.devDependency
@angular-devkit/build-angular was updated from 0.6.8
to 0.8.5
.devDependency
@angular-devkit/build-angular was updated from 0.6.8
to 0.10.0
.devDependency
@angular-devkit/build-angular was updated from 0.6.8
to 0.10.1
.devDependency
@angular-devkit/build-angular was updated from 0.6.8
to 0.10.2
.
Version 0.7.0 of @angular-devkit/build-angular was just published.
The version 0.7.0 is not covered by your current version range.
If you donβt accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.
It might be worth looking into these changes and trying to get this project onto the latest version of @angular-devkit/build-angular.
If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you donβt have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.
FAQ and help
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those donβt help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper bot :palm_tree: