Closed greenkeeper[bot] closed 5 years ago
After pinning to 1.3.0 your tests are passing again. Downgrade this dependency đź“Ś.
devDependency
aws-cdk was updated from 1.3.0
to 1.4.0
.devDependency
@aws-cdk/aws-apigateway was updated from 1.3.0
to 1.4.0
.devDependency
@aws-cdk/aws-codebuild was updated from 1.3.0
to 1.4.0
.devDependency
@aws-cdk/aws-codepipeline was updated from 1.3.0
to 1.4.0
.devDependency
@aws-cdk/aws-iam was updated from 1.3.0
to 1.4.0
.devDependency
@aws-cdk/aws-lambda was updated from 1.3.0
to 1.4.0
.devDependency
@aws-cdk/aws-logs was updated from 1.3.0
to 1.4.0
.devDependency
@aws-cdk/aws-s3 was updated from 1.3.0
to 1.4.0
.devDependency
@aws-cdk/aws-sqs was updated from 1.3.0
to 1.4.0
.devDependency
@aws-cdk/aws-ssm was updated from 1.3.0
to 1.4.0
.devDependency
@aws-cdk/core was updated from 1.3.0
to 1.4.0
.Your tests are passing again with this update. Explicitly upgrade to these versions 🚀
ref
(#3258) (254f62c)defaultChild
(#3572) (c95eab6), closes #3478addAlias
calls on single key (#3596) (54f8ea9)GenericWindowsImage
(#3454) (f4ca41c), closes #3400defaultCapacity: 0
if you wish to disable.:tada: This issue has been resolved in version 1.0.2 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:
There have been updates to the aws-cdk monorepo:
devDependency
@aws-cdk/aws-apigateway was updated from1.3.0
to1.4.0
.devDependency
@aws-cdk/aws-codebuild was updated from1.3.0
to1.4.0
.devDependency
@aws-cdk/aws-codepipeline was updated from1.3.0
to1.4.0
.devDependency
@aws-cdk/aws-iam was updated from1.3.0
to1.4.0
.devDependency
@aws-cdk/aws-logs was updated from1.3.0
to1.4.0
.devDependency
@aws-cdk/core was updated from1.3.0
to1.4.0
.🚨 View failing branch.
This version is covered by your current version range and after updating it in your project the build failed.
This monorepo update includes releases of one or more dependencies which all belong to the aws-cdk group definition.
aws-cdk 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
- ❌ **AWS CodeBuild eu-central-1 (bdd-feature-runner-aws-example-ci):** Build failed for project bdd-feature-runner-aws-example-ci ([Details](https://eu-central-1.console.aws.amazon.com/codebuild/home?region=eu-central-1#/builds/bdd-feature-runner-aws-example-ci:4a11c3e5-e1e2-4608-b2af-f6e6888dd3b3/view/new)).Release Notes for v1.4.0
Bug Fixes
ref
(#3258) (254f62c)defaultChild
(#3572) (c95eab6), closes #3478addAlias
calls on single key (#3596) (54f8ea9)Code Refactoring
Features
GenericWindowsImage
(#3454) (f4ca41c), closes #3400BREAKING CHANGES
You can specify
defaultCapacity: 0
if you wish to disable.For a sync task, users should use "serviceIntegrationPattern: sfn.ServiceIntegrationPattern.SYNC" in the place of "synchronous: true".
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: