An in-range update of worker-timers-broker is breaking the build π¨
greenkeeper opened this issue Β· comments
π¨ 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 worker-timers-broker was updated from 6.0.10
to 6.0.11
.
π¨ View failing branch.
This version is covered by your current version range and after updating it in your project the build failed.
worker-timers-broker 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).
Release Notes for v6.0.11
Commits
The new version differs by 29 commits.
eaa6a86
6.0.11
48331de
fix(package): update worker-timers-worker to version 6.0.8
ad3377f
fix(package): update tslint-config-holy-grail to version 50.0.0
8cab2f4
fix(package): update ts-loader to version 7.0.5
ce4cc27
fix(package): update rollup to version 2.10.9
a103021
fix(package): update mocha to version 7.2.0
57c7c8d
fix(package): update karma-sauce-launcher to version 4.1.5
e7322ec
fix(package): update fast-unique-numbers to version 5.0.8
f837753
fix(package): update eslint to version 7.1.0
b288404
fix(package): update @babel/runtime to version 7.10.0
8db2caf
fix(package): update @babel/preset-env to version 7.10.0
154a54d
fix(package): update @babel/plugin-transform-runtime to version 7.10.0
64550ef
fix(package): update @babel/core to version 7.10.0
0a5f4f4
fix(package): update tslint-config-holy-grail to version 49.0.9
27efd1f
fix(package): update tsconfig-holy-grail to version 11.0.13
There are 29 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 π΄
After pinning to 6.0.10 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.