Skip to content

Bump awsCdkVersion from 1.93.0 to 1.94.1 in /master-cdk #1834

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 1 commit into from
Mar 17, 2021
Merged

Bump awsCdkVersion from 1.93.0 to 1.94.1 in /master-cdk #1834

merged 1 commit into from
Mar 17, 2021

Conversation

@dependabot
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Mar 17, 2021

Bumps awsCdkVersion from 1.93.0 to 1.94.1.
Updates core from 1.93.0 to 1.94.1

Release notes

Sourced from core's releases.

v1.94.1

Bug Fixes

  • s3: Notifications fail to deploy due to incompatible node runtime (#13624) (26bc3d4)

v1.94.0

⚠ BREAKING CHANGES TO EXPERIMENTAL FEATURES

  • appmesh: Backend, backend default and Virtual Service client policies structures are being altered
  • appmesh: you must use the backend default interface to define backend defaults in VirtualGateway. The property name also changed from backendsDefaultClientPolicy to backendDefaults
  • appmesh: you must use the backend default interface to define backend defaults in VirtualNode, (the property name also changed from backendsDefaultClientPolicy to backendDefaults), and the Backend class to define a backend
  • appmesh: you can no longer attach a client policy to a VirtualService

Features

Bug Fixes

Changelog

Sourced from core's changelog.

1.94.1 (2021-03-16)

Bug Fixes

  • s3: Notifications fail to deploy due to incompatible node runtime (#13624) (26bc3d4)

1.94.0 (2021-03-16)

⚠ BREAKING CHANGES TO EXPERIMENTAL FEATURES

  • appmesh: Backend, backend default and Virtual Service client policies structures are being altered
  • appmesh: you must use the backend default interface to define backend defaults in VirtualGateway. The property name also changed from backendsDefaultClientPolicy to backendDefaults
  • appmesh: you must use the backend default interface to define backend defaults in VirtualNode, (the property name also changed from backendsDefaultClientPolicy to backendDefaults), and the Backend class to define a backend
  • appmesh: you can no longer attach a client policy to a VirtualService

Features

Bug Fixes

Commits
  • 60d8f91 chore(release): 1.94.1 (#13625)
  • 3d65124 Error instead of error
  • f3102ed fix changelog heading
  • 818d943 chore(release): 1.94.1
  • 26bc3d4 fix(s3): Notifications fail to deploy due to incompatible node runtime (#13624)
  • 2c1c0eb chore(release): 1.94.0 (#13612)
  • 64dea7c chore(release): 1.94.0
  • 8c6b3eb fix(ec2): Security Groups support all protocols (#13593)
  • 0ec302f chore(region-info): metadata service is in eu-south-1, af-south-1 (#13598)
  • e80a98a feat(ecs-patterns): Add ECS deployment circuit breaker support to higher-leve...
  • Additional commits viewable in compare view

Updates iam from 1.93.0 to 1.94.1

Release notes

Sourced from iam's releases.

v1.94.1

Bug Fixes

  • s3: Notifications fail to deploy due to incompatible node runtime (#13624) (26bc3d4)

v1.94.0

⚠ BREAKING CHANGES TO EXPERIMENTAL FEATURES

  • appmesh: Backend, backend default and Virtual Service client policies structures are being altered
  • appmesh: you must use the backend default interface to define backend defaults in VirtualGateway. The property name also changed from backendsDefaultClientPolicy to backendDefaults
  • appmesh: you must use the backend default interface to define backend defaults in VirtualNode, (the property name also changed from backendsDefaultClientPolicy to backendDefaults), and the Backend class to define a backend
  • appmesh: you can no longer attach a client policy to a VirtualService

Features

Bug Fixes

Changelog

Sourced from iam's changelog.

1.94.1 (2021-03-16)

Bug Fixes

  • s3: Notifications fail to deploy due to incompatible node runtime (#13624) (26bc3d4)

1.94.0 (2021-03-16)

⚠ BREAKING CHANGES TO EXPERIMENTAL FEATURES

  • appmesh: Backend, backend default and Virtual Service client policies structures are being altered
  • appmesh: you must use the backend default interface to define backend defaults in VirtualGateway. The property name also changed from backendsDefaultClientPolicy to backendDefaults
  • appmesh: you must use the backend default interface to define backend defaults in VirtualNode, (the property name also changed from backendsDefaultClientPolicy to backendDefaults), and the Backend class to define a backend
  • appmesh: you can no longer attach a client policy to a VirtualService

Features

Bug Fixes

Commits
  • 60d8f91 chore(release): 1.94.1 (#13625)
  • 3d65124 Error instead of error
  • f3102ed fix changelog heading
  • 818d943 chore(release): 1.94.1
  • 26bc3d4 fix(s3): Notifications fail to deploy due to incompatible node runtime (#13624)
  • 2c1c0eb chore(release): 1.94.0 (#13612)
  • 64dea7c chore(release): 1.94.0
  • 8c6b3eb fix(ec2): Security Groups support all protocols (#13593)
  • 0ec302f chore(region-info): metadata service is in eu-south-1, af-south-1 (#13598)
  • e80a98a feat(ecs-patterns): Add ECS deployment circuit breaker support to higher-leve...
  • Additional commits viewable in compare view

Updates sqs from 1.93.0 to 1.94.1

Release notes

Sourced from sqs's releases.

v1.94.1

Bug Fixes

  • s3: Notifications fail to deploy due to incompatible node runtime (#13624) (26bc3d4)

v1.94.0

⚠ BREAKING CHANGES TO EXPERIMENTAL FEATURES

  • appmesh: Backend, backend default and Virtual Service client policies structures are being altered
  • appmesh: you must use the backend default interface to define backend defaults in VirtualGateway. The property name also changed from backendsDefaultClientPolicy to backendDefaults
  • appmesh: you must use the backend default interface to define backend defaults in VirtualNode, (the property name also changed from backendsDefaultClientPolicy to backendDefaults), and the Backend class to define a backend
  • appmesh: you can no longer attach a client policy to a VirtualService

Features

Bug Fixes

Changelog

Sourced from sqs's changelog.

1.94.1 (2021-03-16)

Bug Fixes

  • s3: Notifications fail to deploy due to incompatible node runtime (#13624) (26bc3d4)

1.94.0 (2021-03-16)

⚠ BREAKING CHANGES TO EXPERIMENTAL FEATURES

  • appmesh: Backend, backend default and Virtual Service client policies structures are being altered
  • appmesh: you must use the backend default interface to define backend defaults in VirtualGateway. The property name also changed from backendsDefaultClientPolicy to backendDefaults
  • appmesh: you must use the backend default interface to define backend defaults in VirtualNode, (the property name also changed from backendsDefaultClientPolicy to backendDefaults), and the Backend class to define a backend
  • appmesh: you can no longer attach a client policy to a VirtualService

Features

Bug Fixes

Commits
  • 60d8f91 chore(release): 1.94.1 (#13625)
  • 3d65124 Error instead of error
  • f3102ed fix changelog heading
  • 818d943 chore(release): 1.94.1
  • 26bc3d4 fix(s3): Notifications fail to deploy due to incompatible node runtime (#13624)
  • 2c1c0eb chore(release): 1.94.0 (#13612)
  • 64dea7c chore(release): 1.94.0
  • 8c6b3eb fix(ec2): Security Groups support all protocols (#13593)
  • 0ec302f chore(region-info): metadata service is in eu-south-1, af-south-1 (#13598)
  • e80a98a feat(ecs-patterns): Add ECS deployment circuit breaker support to higher-leve...
  • Additional commits viewable in compare view

Updates iot from 1.93.0 to 1.94.1

Release notes

Sourced from iot's releases.

v1.94.1

Bug Fixes

  • s3: Notifications fail to deploy due to incompatible node runtime (#13624) (26bc3d4)

v1.94.0

⚠ BREAKING CHANGES TO EXPERIMENTAL FEATURES

  • appmesh: Backend, backend default and Virtual Service client policies structures are being altered
  • appmesh: you must use the backend default interface to define backend defaults in VirtualGateway. The property name also changed from backendsDefaultClientPolicy to backendDefaults
  • appmesh: you must use the backend default interface to define backend defaults in VirtualNode, (the property name also changed from backendsDefaultClientPolicy to backendDefaults), and the Backend class to define a backend
  • appmesh: you can no longer attach a client policy to a VirtualService

Features

Bug Fixes

Changelog

Sourced from iot's changelog.

1.94.1 (2021-03-16)

Bug Fixes

  • s3: Notifications fail to deploy due to incompatible node runtime (#13624) (26bc3d4)

1.94.0 (2021-03-16)

⚠ BREAKING CHANGES TO EXPERIMENTAL FEATURES

  • appmesh: Backend, backend default and Virtual Service client policies structures are being altered
  • appmesh: you must use the backend default interface to define backend defaults in VirtualGateway. The property name also changed from backendsDefaultClientPolicy to backendDefaults
  • appmesh: you must use the backend default interface to define backend defaults in VirtualNode, (the property name also changed from backendsDefaultClientPolicy to backendDefaults), and the Backend class to define a backend
  • appmesh: you can no longer attach a client policy to a VirtualService

Features

Bug Fixes

Commits
  • 60d8f91 chore(release): 1.94.1 (#13625)
  • 3d65124 Error instead of error
  • f3102ed fix changelog heading
  • 818d943 chore(release): 1.94.1
  • 26bc3d4 fix(s3): Notifications fail to deploy due to incompatible node runtime (#13624)
  • 2c1c0eb chore(release): 1.94.0 (#13612)
  • 64dea7c chore(release): 1.94.0
  • 8c6b3eb fix(ec2): Security Groups support all protocols (#13593)
  • 0ec302f chore(region-info): metadata service is in eu-south-1, af-south-1 (#13598)
  • e80a98a feat(ecs-patterns): Add ECS deployment circuit breaker support to higher-leve...
  • Additional commits viewable in compare view

Updates lambda from 1.93.0 to 1.94.1

Release notes

Sourced from lambda's releases.

v1.94.1

Bug Fixes

  • s3: Notifications fail to deploy due to incompatible node runtime (#13624) (26bc3d4)

v1.94.0

⚠ BREAKING CHANGES TO EXPERIMENTAL FEATURES

  • appmesh: Backend, backend default and Virtual Service client policies structures are being altered
  • appmesh: you must use the backend default interface to define backend defaults in VirtualGateway. The property name also changed from backendsDefaultClientPolicy to backendDefaults
  • appmesh: you must use the backend default interface to define backend defaults in VirtualNode, (the property name also changed from backendsDefaultClientPolicy to backendDefaults), and the Backend class to define a backend
  • appmesh: you can no longer attach a client policy to a VirtualService

Features

Bug Fixes

Changelog

Sourced from lambda's changelog.

1.94.1 (2021-03-16)

Bug Fixes

  • s3: Notifications fail to deploy due to incompatible node runtime (#13624) (26bc3d4)

1.94.0 (2021-03-16)

⚠ BREAKING CHANGES TO EXPERIMENTAL FEATURES

  • appmesh: Backend, backend default and Virtual Service client policies structures are being altered
  • appmesh: you must use the backend default interface to define backend defaults in VirtualGateway. The property name also changed from backendsDefaultClientPolicy to backendDefaults
  • appmesh: you must use the backend default interface to define backend defaults in VirtualNode, (the property name also changed from backendsDefaultClientPolicy to backendDefaults), and the Backend class to define a backend
  • appmesh: you can no longer attach a client policy to a VirtualService

Features

Bug Fixes

Commits
  • 60d8f91 chore(release): 1.94.1 (#13625)
  • 3d65124 Error instead of error
  • f3102ed fix changelog heading
  • 818d943 chore(release): 1.94.1
  • 26bc3d4 fix(s3): Notifications fail to deploy due to incompatible node runtime (#13624)
  • 2c1c0eb chore(release): 1.94.0 (#13612)
  • 64dea7c chore(release): 1.94.0
  • 8c6b3eb fix(ec2): Security Groups support all protocols (#13593)
  • 0ec302f chore(region-info): metadata service is in eu-south-1, af-south-1 (#13598)
  • e80a98a feat(ecs-patterns): Add ECS deployment circuit breaker support to higher-leve...
  • Additional commits viewable in compare view

Updates dynamodb from 1.93.0 to 1.94.1

Release notes

Sourced from dynamodb's releases.

v1.94.1

Bug Fixes

  • s3: Notifications fail to deploy due to incompatible node runtime (#13624) (26bc3d4)

v1.94.0

⚠ BREAKING CHANGES TO EXPERIMENTAL FEATURES

  • appmesh: Backend, backend default and Virtual Service client policies structures are being altered
  • appmesh: you must use the backend default interface to define backend defaults in VirtualGateway. The property name also changed from backendsDefaultClientPolicy to backendDefaults
  • appmesh: you must use the backend default interface to define backend defaults in VirtualNode, (the property name also changed from backendsDefaultClientPolicy to backendDefaults), and the Backend class to define a backend
  • appmesh: you can no longer attach a client policy to a VirtualService

Features

Bug Fixes

Changelog

Sourced from dynamodb's changelog.

1.94.1 (2021-03-16)

Bug Fixes

  • s3: Notifications fail to deploy due to incompatible node runtime (#13624) (26bc3d4)

1.94.0 (2021-03-16)

⚠ BREAKING CHANGES TO EXPERIMENTAL FEATURES

  • appmesh: Backend, backend default and Virtual Service client policies structures are being altered
  • appmesh: you must use the backend default interface to define backend defaults in VirtualGateway. The property name also changed from backendsDefaultClientPolicy to backendDefaults
  • appmesh: you must use the backend default interface to define backend defaults in VirtualNode, (the property name also changed from backendsDefaultClientPolicy to backendDefaults), and the Backend class to define a backend
  • appmesh: you can no longer attach a client policy to a VirtualService

Features

Bug Fixes

Commits
  • 60d8f91 chore(release): 1.94.1 (#13625)
  • 3d65124 Error instead of error
  • f3102ed fix changelog heading
  • 818d943 chore(release): 1.94.1
  • 26bc3d4 fix(s3): Notifications fail to deploy due to incompatible node runtime (#13624)
  • 2c1c0eb chore(release): 1.94.0 (#13612)
  • 64dea7c chore(release): 1.94.0
  • 8c6b3eb fix(ec2): Security Groups support all protocols (#13593)
  • 0ec302f chore(region-info): metadata service is in eu-south-1, af-south-1 (#13598)
  • e80a98a feat(ecs-patterns): Add ECS deployment circuit breaker support to higher-leve...
  • Additional commits viewable in compare view

Updates apigateway from 1.93.0 to 1.94.1

Release notes

Sourced from apigateway's releases.

v1.94.1

Bug Fixes

  • s3: Notifications fail to deploy due to incompatible node runtime (#13624) (26bc3d4)

v1.94.0

⚠ BREAKING CHANGES TO EXPERIMENTAL FEATURES

  • appmesh: Backend, backend default and Virtual Service client policies structures are being altered
  • appmesh: you must use the backend default interface to define backend defaults in VirtualGateway. The property name also changed from backendsDefaultClientPolicy to backendDefaults
  • appmesh: you must use the backend default interface to define backend defaults in VirtualNode, (the property name also changed from backendsDefaultClientPolicy to backendDefaults), and the Backend class to define a backend
  • appmesh: you can no longer attach a client policy to a VirtualService

Features

Bug Fixes

Changelog

Sourced from apigateway's changelog.

1.94.1 (2021-03-16)

Bug Fixes

  • s3: Notifications fail to deploy due to incompatible node runtime (#13624) (26bc3d4)

1.94.0 (2021-03-16)

⚠ BREAKING CHANGES TO EXPERIMENTAL FEATURES

  • appmesh: Backend, backend default and Virtual Service client policies structures are being altered
  • appmesh: you must use the backend default interface to define backend defaults in VirtualGateway. The property name also changed from backendsDefaultClientPolicy to backendDefaults
  • appmesh: you must use the backend default interface to define backend defaults in VirtualNode, (the property name also changed from backendsDefaultClientPolicy to backendDefaults), and the Backend class to define a backend
  • appmesh: you can no longer attach a client policy to a VirtualService

Features

Bug Fixes

Commits
  • 60d8f91 chore(release): 1.94.1 (#13625)
  • 3d65124 Error instead of error
  • f3102ed fix changelog heading
  • 818d943 chore(release): 1.94.1
  • 26bc3d4 fix(s3): Notifications fail to deploy due to incompatible node runtime (#13624)
  • 2c1c0eb chore(release): 1.94.0 (#13612)
  • 64dea7c chore(release): 1.94.0
  • 8c6b3eb fix(ec2): Security Groups support all protocols (#13593)
  • 0ec302f chore(region-info): metadata service is in eu-south-1, af-south-1 (#13598)
  • e80a98a feat(ecs-patterns): Add ECS deployment circuit breaker support to higher-leve...
  • Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

@dependabot
Bump awsCdkVersion from 1.93.0 to 1.94.1 in /master-cdk
f1e077d 
Bumps `awsCdkVersion` from 1.93.0 to 1.94.1.

Updates `core` from 1.93.0 to 1.94.1
- [Release notes](https://github.com/aws/aws-cdk/releases)
- [Changelog](https://github.com/aws/aws-cdk/blob/master/CHANGELOG.md)
- [Commits](aws/aws-cdk@v1.93.0...v1.94.1)

Updates `iam` from 1.93.0 to 1.94.1
- [Release notes](https://github.com/aws/aws-cdk/releases)
- [Changelog](https://github.com/aws/aws-cdk/blob/master/CHANGELOG.md)
- [Commits](aws/aws-cdk@v1.93.0...v1.94.1)

Updates `sqs` from 1.93.0 to 1.94.1
- [Release notes](https://github.com/aws/aws-cdk/releases)
- [Changelog](https://github.com/aws/aws-cdk/blob/master/CHANGELOG.md)
- [Commits](aws/aws-cdk@v1.93.0...v1.94.1)

Updates `iot` from 1.93.0 to 1.94.1
- [Release notes](https://github.com/aws/aws-cdk/releases)
- [Changelog](https://github.com/aws/aws-cdk/blob/master/CHANGELOG.md)
- [Commits](aws/aws-cdk@v1.93.0...v1.94.1)

Updates `lambda` from 1.93.0 to 1.94.1
- [Release notes](https://github.com/aws/aws-cdk/releases)
- [Changelog](https://github.com/aws/aws-cdk/blob/master/CHANGELOG.md)
- [Commits](aws/aws-cdk@v1.93.0...v1.94.1)

Updates `dynamodb` from 1.93.0 to 1.94.1
- [Release notes](https://github.com/aws/aws-cdk/releases)
- [Changelog](https://github.com/aws/aws-cdk/blob/master/CHANGELOG.md)
- [Commits](aws/aws-cdk@v1.93.0...v1.94.1)

Updates `apigateway` from 1.93.0 to 1.94.1
- [Release notes](https://github.com/aws/aws-cdk/releases)
- [Changelog](https://github.com/aws/aws-cdk/blob/master/CHANGELOG.md)
- [Commits](aws/aws-cdk@v1.93.0...v1.94.1)

Signed-off-by: dependabot[bot] <[email protected]>
@timmattison timmattison merged commit a06f100 into master Mar 17, 2021
@timmattison timmattison deleted the dependabot/gradle/master-cdk/awsCdkVersion-1.94.1 branch July 15, 2022 13:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

(aws-applicationautoscaling): Cannot use percentile metrics for step scaling (elasticloadbalancingv2): cant set protocol version on alb aws-ecs-patterns: Add CircuitBreaker pattern for ApplicationLoadBalancedFargateService (aws-appmesh): Client Policies object should not be part of the Virtual Service [appmesh] Implement missing Route Match features
(aws-ec2): cannot create ingress rule for protocols ESP or AH (Cloudwatch): Metrics with labels can't be used in alarms for API Gateway metrics (aws-lambda): fromDockerBuild output is located incorrectly cdk-core: custom resource framework lambda functions created with deprecated version nodejs10.x (region-info): aws-entities.ts AWS_REGIONS missing ap-northeast-3

1 participant

@timmattison