Update tape to the latest version 🚀#90
Merged
geraintwhite merged 1 commit intomasterfrom Feb 19, 2018
Merged
Conversation
Member
|
🎉 This PR is included in version 4.1.2 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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.9.0 of tape was just published.
The version 4.9.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 tape.
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 27 commits.
ea6d91ev4.9.06867840[Deps] updateobject-inspect,resolve4919e40[Tests] onnodev9; usenvm install-latest-npmf26375cMerge pull request #420 from inadarei/global-depth-env-var17276d7[New] useprocess.env.NODE_TAPE_OBJECT_PRINT_DEPTHfor the default object print depth.0e870c6Merge pull request #408 from johnhenry/feature/on-failure00aa133Add "onFinish" listener to test harness.0e68b2d[Dev Deps] updatejs-yaml10b7dcd[Fix] fix stack where actual is falsy13173a5Merge pull request #402 from nhamer/stack_stripf90e487normalize path separators in stacksb66f8f8[Deps] updatefunction-bindcc69501Merge pull request #387 from fongandrew/masterbf5a750Handle spaces in path name for setting file, line no3c2087aTest name with spacesThere are 27 commits in total.
See the full diff
FAQ and help
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper bot 🌴