This repository was archived by the owner on Apr 29, 2020. It is now read-only.
Open
Conversation
Codecov Report
@@ Coverage Diff @@
## master #60 +/- ##
=====================================
Coverage 100% 100%
=====================================
Files 7 7
Lines 92 92
Branches 7 7
=====================================
Hits 92 92Continue to review full report at Codecov.
|
Author
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Version 4.7.0 of tape just got published.
The version 4.7.0 is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of tape.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Commits
The new version differs by 19 commits.
1d0df26v4.7.051597e2Merge pull request #374 from feross/masterb06f914[Refactor] instead of throwing onundefined.forEach, throw explicitly.dd93216[Fix] fix spurious "test exited without ending"1a8e936[Deps] updateglob,resolve7eb9e36[Dev Deps] updatefalafel,js-yamle030260[Tests] onnodev8; no need for sudo;v0.8passes now; allow v5/v7/iojs to fail.4375661[Tests] npm v5+ breaks on node < v4df48bfaOnly apps should have lock files.35e47e1[Tests] npm v4.6+ breaks on node < v1dc1ffa5[Deps] updateobject-inspect66519cb[Deps] updateresolvee6d4625[Dev Deps] updateconcat-stream,js-yamlbdf2b04tap-min moved to derhuerst/tap-min8b3a77e[Tests] fix thrower stack in node 0.8There are 19 commits in total.
See the full diff
Not sure how things should work exactly?
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴