Bump aws-cdk-aws-route53-targets from 1.93.0 to 1.94.1

[dependabot]

Bumps aws-cdk-aws-route53-targets from 1.93.0 to 1.94.1.

Release notes

Sourced from aws-cdk-aws-route53-targets'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

• appmesh: add missing route match features (#13350) (b71efd9), closes #11645
• aws-elasticloadbalancingv2: add protocol version for ALB TargetGroups (#13570) (165a3d8), closes #12869
• ecs-patterns: Add ECS deployment circuit breaker support to higher-level constructs (#12719) (e80a98a), closes #12534 #12360

Bug Fixes

• appmesh: Move Client Policy from Virtual Service to backend structure (#12943) (d3f4284), closes #11996
• autoscaling: AutoScaling on percentile metrics doesn't work (#13366) (46114bb), closes #13144
• cloudwatch: cannot create Alarms from labeled metrics that start with a digit (#13560) (278029f), closes #13434
• use NodeJS 14 for all packaged custom resources (#13488) (20a2820), closes #13534 #13484
• ec2: Security Groups support all protocols (#13593) (8c6b3eb), closes #13403
• lambda: fromDockerBuild output is located under /asset (#13539) (77449f6), closes #13439
• region-info: ap-northeast-3 data not correctly registered (#13564) (64da84b), closes #13561

Changelog

Sourced from aws-cdk-aws-route53-targets'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

• appmesh: add missing route match features (#13350) (b71efd9), closes #11645
• aws-elasticloadbalancingv2: add protocol version for ALB TargetGroups (#13570) (165a3d8), closes #12869
• ecs-patterns: Add ECS deployment circuit breaker support to higher-level constructs (#12719) (e80a98a), closes #12534 #12360

Bug Fixes

• appmesh: Move Client Policy from Virtual Service to backend structure (#12943) (d3f4284), closes #11996
• autoscaling: AutoScaling on percentile metrics doesn't work (#13366) (46114bb), closes #13144
• cloudwatch: cannot create Alarms from labeled metrics that start with a digit (#13560) (278029f), closes #13434
• use NodeJS 14 for all packaged custom resources (#13488) (20a2820), closes #13534 #13484
• ec2: Security Groups support all protocols (#13593) (8c6b3eb), closes #13403
• lambda: fromDockerBuild output is located under /asset (#13539) (77449f6), closes #13439
• region-info: ap-northeast-3 data not correctly registered (#13564) (64da84b), closes #13561

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]

Looks like aws-cdk-aws-route53-targets is up-to-date now, so this is no longer needed.