Open greenkeeper[bot] opened 6 years ago
Merging #108 into master will not change coverage. The diff coverage is
n/a
.
@@ Coverage Diff @@
## master #108 +/- ##
=====================================
Coverage 100% 100%
=====================================
Files 5 5
Lines 10 10
Branches 1 1
=====================================
Hits 10 10
Update to this version instead š
The new version differs by 11 commits.
ea09e05
chore: release 0.6.0
4a23f86
chore: Fixed xo warning on collectFlowCoverageForFile parameters
84ef534
feat: Added --percent-decimals cli options
39f3a98
chore: Optionally round percent values with decimals
6503925
fix: Fixed deprecated config names and improve cli/config type checks
b6b63b9
chore: Removed redundant filename in coverage collection error message
533d94f
fix: Fixed flow-command-path yargs coerce function
31af708
chore: Added isFlowAnnotation helper and stored result into fileCoverageData.isFlow
3abe6bf
fix: Added support for the new flow annotations (strict and strict-local)
5a72d56
chore: Minor changes to the excludeNonFlow mode and flow-typed libdefs update script
6737621
feat: Added a new --exclude-non-flow cli option
See the full diff
devDependency
flow-coverage-report was updated from 0.4.1
to 0.6.1
.Update to this version instead š
The new version differs by 4 commits.
43c311c
chore(travis): don't exclude tagged release from travis deploy stage
f4ca40a
chore: release 0.6.1
8160cf2
fix(package): Change badge-up to @rpl/badge-up to fix vulnerable dependency issue (#178)
5dd06d6
chore(travis): update travis file npm config
See the full diff
devDependency
flow-coverage-report was updated from 0.4.1
to 0.6.2
.devDependency
flow-coverage-report was updated from 0.4.1
to 0.7.0
.
āļø Greenkeeperās updated Terms of Service will come into effect on April 6th, 2018.
Version 0.5.0 of flow-coverage-report was just published.
The version 0.5.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 flow-coverage-report.
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.
Commits
The new version differs by 11 commits.
43d855d
fix(travis): added branch to travis deploy section
0f9b811
chore: release 0.5.0
8ad8d58
chore(travis): Release new tags as new npm release from Travis.
58b6b94
feat: Implement a new --strict-coverage option to enforce a more strict coverage reporting mode.
cda4747
test: Added new integration test for the badge reporter
1941fc5
feat: Run badge reporter implicitly when html report type has been included.
520f137
test: Added new test unit for the report-badge module
48c986d
feat: Minor tweaks and added flow badge to the new badge reporter
040c798
fix(jest): Fixed jest issues with svgo badge dependency
90884f7
chore(package): Updated jest to 22.1.1 and babel-jest to 22.1.0
c913d5a
feat: Add a new badge reporter
See the full diff
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: