-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
An in-range update of async-lock is breaking the build 🚨 #49
Comments
After pinning to 1.1.4 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results. |
Your tests are still failing with this version. Compare changes |
Your tests are still failing with this version. Compare changes |
Your tests are still failing with this version. Compare changes CommitsThe new version differs by 6 commits.
See the full diff |
Your tests are still failing with this version. Compare changes |
The dependency async-lock was updated from
1.1.4
to1.2.0
.🚨 View failing branch.
This version is covered by your current version range and after updating it in your project the build failed.
async-lock 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
Release Notes for add ES5 compliance
Fixes #21
Commits
The new version differs by 3 commits.
6fb6344
v1.2.0
3659c75
Merge pull request #23 from paulroub/fix-es5
51a2b4b
Fix ES5 compatibility per #21
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 🌴
The text was updated successfully, but these errors were encountered: