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 aws-sdk is breaking the build 🚨 #90

Closed greenkeeper[bot] closed 6 years ago

greenkeeper[bot] commented 6 years ago

Version 2.312.0 of aws-sdk was just published.

Branch Build failing 🚨
Dependency aws-sdk
Current Version 2.311.0
Type devDependency

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

aws-sdk 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:** AppVeyor build failed ([Details](https://ci.appveyor.com/project/balassy/aws-lambda-typescript/build/1.0.360)). - ❌ **continuous-integration/travis-ci/push:** The Travis CI build could not complete due to an error ([Details](https://travis-ci.org/balassy/aws-lambda-typescript/builds/427014543?utm_source=github_status&utm_medium=notification)).
Release Notes Release v2.312.0

See changelog for more information.

Commits

The new version differs by 6 commits.

  • 4ed5104 Updates SDK to v2.312.0
  • 3839328 Create no-response.yml
  • 59f1eb0 remove stalebot
  • 23701ac enable stale bot
  • f5a3482 update typings for credentialsProviderChain & httpOptions (#2240)
  • 167bc31 retry request for Batch TooManyRequestsException (#2246)

See the full diff

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 2.311.0 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

Fixed with manually updating to 2.312.0 in PR #91 .

greenkeeper[bot] commented 6 years ago

Version 2.313.0 just got published.

Your tests are passing again with this version. Explicitly upgrade to this version 🚀

Release Notes Release v2.313.0

See changelog for more information.

Commits

The new version differs by 1 commits.

See the full diff