Skip to content
This repository has been archived by the owner on Feb 23, 2022. It is now read-only.

chore(deps-dev): bump @aws-cdk/aws-lambda-nodejs from 1.92.0 to 1.94.1 #14

Conversation

dependabot[bot]
Copy link
Contributor

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

Bumps @aws-cdk/aws-lambda-nodejs from 1.92.0 to 1.94.1.

Release notes

Sourced from @​aws-cdk/aws-lambda-nodejs'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

v1.93.0

Features

... (truncated)

Changelog

Sourced from @​aws-cdk/aws-lambda-nodejs'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

1.93.0 (2021-03-11)

Features

... (truncated)

Commits

Dependabot compatibility score

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 dependabot bot added the dependencies Pull requests that update a dependency file label Mar 17, 2021
@iliapolo
Copy link
Contributor

Dependabot should be updating @aws-cdk packages since they must all be updated together

@iliapolo iliapolo closed this Mar 19, 2021
@iliapolo iliapolo deleted the dependabot/npm_and_yarn/aws-cdk/aws-lambda-nodejs-1.94.1 branch March 19, 2021 09:39
@dependabot @github
Copy link
Contributor Author

dependabot bot commented on behalf of github Mar 19, 2021

OK, I won't notify you again about this release, but will get in touch when a new version is available.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.