-
Notifications
You must be signed in to change notification settings - Fork 120
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 express-status-monitor is breaking the build 🚨 #102
Comments
After pinning to 1.1.5 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 19 commits.
There are 19 commits in total. See the full diff |
Your tests are still failing with this version. Compare changes |
The dependency express-status-monitor was updated from
1.1.5
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.
express-status-monitor 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
Commits
The new version differs by 9 commits.
8a415e8
Release 1.2.0
25e8100
Merge pull request #104 from bcdxn/master
6699925
Improve example
81e2361
Merge branch 'master' into master
f15d2c1
Merge branch 'master' of https://github.com/RafalWilinski/express-status-monitor
2e08e51
Remove commented out code
fa55b2c
Add health checks
448d1e0
Merge pull request #102 from tkruczek/master
761b01d
Set ignoreStartsWith to /admin
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: