search

chrisguttandin / midi-json-parser-worker

The worker which is used by the midi-json-parser package.
MIT License
6 stars 1 forks source link

An in-range update of rollup is breaking the build 🚨 #257

Closed greenkeeper[bot] closed 5 years ago

greenkeeper[bot] commented 5 years ago

The devDependency rollup was updated from 1.14.0 to 1.14.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

rollup is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details - ❌ **continuous-integration/travis-ci/push:** The Travis CI build failed ([Details](https://travis-ci.org/chrisguttandin/midi-json-parser-worker/builds/541766825?utm_source=github_status&utm_medium=notification)).
Release Notes for v1.14.1

2019-06-05

Bug Fixes

  • Fix an issue where try-statements were not included properly when a variable declared inside the statement was accessed outside it (#2898)
  • Fix an issue where await expressions were not included properly (#2899)

Pull Requests

  • #2898: Properly include try-catch-statements even if they have already been included in some way (@lukastaegert)
  • #2899: Fix unintended early return in await inclusion handling (@lukastaegert)
Commits

The new version differs by 4 commits.

  • 7915205 1.14.1
  • 4f7fdda Update changelog
  • af1748d Fix unintended early return in await inclusion handling. (#2899)
  • 71f2fa8 Properly include try-catch-statements even if they have already been (#2898)

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:

greenkeeper[bot] commented 5 years ago

After pinning to 1.14.0 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.