• ❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

The new version differs by 10 commits.

• 050b318 v4.9.1
• 73232c0 [Dev Deps] update js-yaml
• 8a2d29b [Deps] update has, for-each, resolve, object-inspect
• c6f5313 [Tests] add eclint and eslint, to enforce a consistent style
• 45788a5 [Dev Deps] update concat-stream
• ec4a71d [fix] Fix bug in functionName regex during stack parsing
• 7261ccc Merge pull request #433 from mcnuttandrew/add-trb
• 6cbc53e Add tap-react-browser
• 9d501ff [Dev Deps] use ~ for dev deps; update to latest nonbreaking
• 24e0a8d Fix spelling of "parameterize"

See the full diff

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Greenkeeper has checked the engines key in any package.json file, the .nvmrc file, and the .travis.yml file, if present.

• engines was only updated if it defined a single version, not a range.
• .nvmrc was updated to Node.js 10
• .travis.yml was only changed if there was a root-level node_js that didn’t already include Node.js 10, such as node or lts/*. In this case, the new version was appended to the list. We didn’t touch job or matrix configurations because these tend to be quite specific and complex, and it’s difficult to infer what the intentions were.

For many simpler .travis.yml configurations, this PR should suffice as-is, but depending on what you’re doing it may require additional work or may not be applicable at all. We’re also aware that you may have good reasons to not update to Node.js 10, which is why this was sent as an issue and not a pull request. Feel free to delete it without comment, I’m a humble robot and won’t feel rejected 🤖

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.