Closed greenkeeper[bot] closed 6 years ago
Merging #50 into next will not change coverage. The diff coverage is
100%
.
@@ Coverage Diff @@
## next #50 +/- ##
===================================
Coverage 100% 100%
===================================
Files 1 1
Lines 13 12 -1
Branches 2 2
===================================
- Hits 13 12 -1
Impacted Files | Coverage Δ | |
---|---|---|
index.js | 100% <100%> (ø) |
: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 1c47524...695b78d. Read the comment docs.
Version 3.0.0 of has-lockfile was just published.
The version 3.0.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 has-lockfile.
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 4 commits.
8e0e396
3.0.0
89cf4ee
refactor: avoid mutating array
31b8cba
feat: detect
npm-shrinkwrap.json
(#8)c862da5
chore: meta tweaks
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: