search

balassy / aws-lambda-typescript

This sample uses the Serverless Application Framework to implement an AWS Lambda function in TypeScript, deploy it via CloudFormation, publish it through API Gateway to a custom domain registered on Route53, and document it with Swagger.
MIT License
267 stars 50 forks source link

An in-range update of @types/aws-lambda is breaking the build 🚨 #93

Closed greenkeeper[bot] closed 6 years ago

greenkeeper[bot] commented 6 years ago

The devDependency @types/aws-lambda was updated from 8.10.11 to 8.10.12.

🚨 View failing branch.

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

@types/aws-lambda is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details - ❌ **continuous-integration/appveyor/branch:** Waiting for AppVeyor build to complete ([Details](https://ci.appveyor.com/project/balassy/aws-lambda-typescript/build/1.0.371)). - ❌ **continuous-integration/travis-ci/push:** The Travis CI build failed ([Details](https://travis-ci.org/balassy/aws-lambda-typescript/builds/428255702?utm_source=github_status&utm_medium=notification)).
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 6 years ago

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

balassy commented 6 years ago

Version 8.10.13 fixed it.