Open greenkeeper[bot] opened 7 years ago
After pinning to 4.0.35 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 the changes π¨
Your tests are still failing with this version. Compare the changes π¨
Your tests are still failing with this version. Compare the changes π¨
Your tests are still failing with this version. Compare the changes π¨
Your tests are still failing with this version. Compare the changes π¨
Your tests are still failing with this version. Compare the changes π¨
devDependency
@types/express was updated from 4.16.0
to 4.16.1
.Your tests are still failing with this version. Compare changes
devDependency
@types/express was updated from 4.16.1
to 4.17.0
.Your tests are still failing with this version. Compare changes
Version 4.0.36 of @types/express just got published.
This version is covered by your current version range and after updating it in your project the build failed.
As @types/express is βonlyβ a devDependency of this project it might not break production or downstream projects, but βonlyβ your build or test tools β preventing new deploys or publishes.
I recommend you give this issue a high priority. Iβm sure you can resolve this :muscle:
Status Details
- β **continuous-integration/travis-ci/push** The Travis CI build is in progress [Details](https://travis-ci.org/alsatian-test/alsatian-website/builds/243410923?utm_source=github_status&utm_medium=notification) - β **continuous-integration/appveyor/branch** AppVeyor build failed [Details](https://ci.appveyor.com/project/jamesrichford/alsatian-website/build/1.0.0-281)Not sure how things should work exactly?
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper Bot :palm_tree: