search

chrisguttandin / json-midi-encoder

This module encodes a JSON representation of MIDI data into a binary MIDI file.
MIT License
41 stars 4 forks source link

An in-range update of json-midi-encoder-worker is breaking the build 🚨 #356

Closed greenkeeper[bot] closed 4 years ago

greenkeeper[bot] commented 4 years ago

🚨 Reminder! Less than one month left to migrate your repositories over to Snyk before Greenkeeper says goodbye on June 3rd! 💜 🚚💨 💚

Find out how to migrate to Snyk at greenkeeper.io

The dependency json-midi-encoder-worker was updated from 5.0.10 to 5.0.11.

🚨 View failing branch.

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

json-midi-encoder-worker is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details - ❌ **continuous-integration/travis-ci/push:** The Travis CI build could not complete due to an error ([Details](https://travis-ci.org/github/chrisguttandin/json-midi-encoder/builds/688168464?utm_source=github_status&utm_medium=notification)).
Release Notes for v5.0.11

all commits

Commits

The new version differs by 8 commits.

  • 7d19fd9 5.0.11
  • 808bc9c fix(package): update tslint-config-holy-grail to version 49.0.7
  • 1dc1386 fix(package): update rollup to version 2.10.2
  • 75a64ec fix(package): update midi-json-parser-worker to version 7.0.10
  • b0364a7 fix(package): update karma to version 5.0.7
  • 80581df fix(package): update json-midi-message-encoder to version 3.0.10
  • f7d1774 fix(package): update eslint-config-holy-grail to version 47.0.0
  • 74a8ee0 fix(package): update eslint to version 7.0.0

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 4 years ago

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