Skip to content
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.

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

chore(deps): update aws-cdk monorepo to v1.98.0 #9

Merged
merged 4 commits into from
Apr 15, 2021

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Oct 10, 2020

WhiteSource Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@aws-cdk/assert 1.66.0 -> 1.98.0 age adoption passing confidence
@aws-cdk/aws-iam 1.66.0 -> 1.98.0 age adoption passing confidence
@aws-cdk/aws-lambda 1.66.0 -> 1.98.0 age adoption passing confidence
@aws-cdk/core 1.66.0 -> 1.98.0 age adoption passing confidence
@aws-cdk/custom-resources 1.66.0 -> 1.98.0 age adoption passing confidence

Release Notes

aws/aws-cdk

v1.98.0

Compare Source

Features
Bug Fixes

v1.97.0

Compare Source

⚠️ BREAKING CHANGES TO EXPERIMENTAL FEATURES
  • elasticsearch: vpcOptions was removed. Use vpc, vpcSubnets and securityGroups instead.
Features
Bug Fixes

v1.96.0

Compare Source

⚠️ BREAKING CHANGES TO EXPERIMENTAL FEATURES
  • globalaccelerator: automatic naming algorithm has been changed: if you have existing Accelerators you will need to pass an
    explicit name to prevent them from being replaced. All endpoints are now added by calling addEndpoint() with a
    target-specific class that can be found in @aws-cdk/aws-globalaccelerator-endpoints. The generated Security Group
    is now looked up by calling endpointGroup.connectionsPeer().
  • docdb: DatabaseClusterProps.instanceProps was hoisted and all its properties are now available one level up directly in DatabaseClusterProps.
  • docdb: DatabaseInstanceProps.instanceClass renamed to DatabaseInstanceProps.instanceType.
  • core: The type of the image property in BundlingOptions
    is changed from BundlingDockerImage to DockerImage.
  • core: The return type of the DockerImage.fromBuild() API is
    changed from BundlingDockerImage to DockerImage.
Features
Bug Fixes

v1.95.2

Compare Source

v1.95.1

Compare Source

Bug Fixes
  • codebuild: module fails to load with error "Cannot use import statement outside a module" (b1ffd33), closes #​13699 #​13699

v1.95.0

Compare Source

⚠️ BREAKING CHANGES TO EXPERIMENTAL FEATURES
  • lambda-nodejs: The type of image property in the
    Bundling class is changed from BundlingDockerImage to
    DockerImage.
  • lambda-nodejs: The type of dockerImage property in
    BundlingOptions is changed from BundlingDockerImage to
    DockerImage.
  • apigatewayv2: The type of allowMethods property under corsPreflight
    section is changed from HttpMethod to CorsHttpMethod.
  • lambda-nodejs: the default runtime of a NodejsFunction is now Node.js 14.x if the environment from which it is deployed uses Node.js >= 14 and Node.js 12.x otherwise.
Features
Bug Fixes

v1.94.1

Compare Source

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

v1.94.0

Compare Source

⚠️ 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

Compare Source

Features
Bug Fixes

v1.92.0

Compare Source

  • ecs-patterns: the desiredCount property stored on the above constructs will be optional, allowing them to be undefined. This is enabled through the @aws-cdk/aws-ecs-patterns:removeDefaultDesiredCount feature flag. We would recommend all CDK users to set the @aws-cdk/aws-ecs-patterns:removeDefaultDesiredCount flag to true for all of their existing applications.
⚠️ BREAKING CHANGES TO EXPERIMENTAL FEATURES
  • apigatewayv2: HttpApiMapping (and related interfaces for Attributed and Props) has been renamed to ApiMapping
  • apigatewayv2: CommonStageOptions has been renamed to StageOptions
  • apigatewayv2: HttpStage.fromStageName has been removed in favour of HttpStage.fromHttpStageAttributes
  • apigatewayv2: DefaultDomainMappingOptions has been removed in favour of DomainMappingOptions
  • apigatewayv2: HttpApiProps.defaultDomainMapping has been changed from DefaultDomainMappingOptions to DomainMappingOptions
  • apigatewayv2: HttpApi.defaultStage has been changed from HttpStage to IStage
  • apigatewayv2: IHttpApi.defaultStage has been removed
  • aws-appsync: RdsDataSource now takes a ServerlessCluster instead of a DatabaseCluster
  • aws-appsync: graphqlapi.addRdsDataSource now takes databaseName as its fourth argument
Features
Bug Fixes

v1.91.0

Compare Source

⚠️ BREAKING CHANGES TO EXPERIMENTAL FEATURES
  • aws-appsync: RdsDataSource now takes a ServerlessCluster instead of a DatabaseCluster
  • aws-appsync: graphqlapi.addRdsDataSource now takes databaseName as its fourth argument
Features
Bug Fixes
  • UserPool, Volume, ElasticSearch, FSx are now RETAIN by default (#​12920) ([5a54741](https://to

Configuration

📅 Schedule: "before 6am,every weekend" in timezone Europe/Oslo.

🚦 Automerge: Disabled due to failing status checks.

♻️ Rebasing: Renovate will not automatically rebase this PR, because other commits have been found.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.


  • If you want to rebase/retry this PR, check this box.

This PR has been generated by WhiteSource Renovate. View repository job log here.

@renovate
Copy link
Contributor Author

renovate bot commented Oct 10, 2020

Branch automerge failure

This PR was configured for branch automerge, however this is not possible so it has been raised as a PR instead.


  • Branch has one or more failed status checks

@renovate renovate bot force-pushed the renovate/aws-cdk-monorepo branch 5 times, most recently from 599f482 to a2adeb1 Compare October 15, 2020 20:00
@renovate renovate bot changed the title chore(deps): update aws-cdk monorepo to v1.67.0 chore(deps): update aws-cdk monorepo Oct 15, 2020
@renovate renovate bot force-pushed the renovate/aws-cdk-monorepo branch from a2adeb1 to c51449f Compare October 15, 2020 20:08
@renovate renovate bot changed the title chore(deps): update aws-cdk monorepo chore(deps): update aws-cdk monorepo to v1.68.0 Oct 15, 2020
@renovate renovate bot force-pushed the renovate/aws-cdk-monorepo branch 8 times, most recently from dc9ac9d to fcd189e Compare October 19, 2020 22:28
@renovate renovate bot changed the title chore(deps): update aws-cdk monorepo to v1.68.0 chore(deps): update aws-cdk monorepo to v1.69.0 Oct 19, 2020
@renovate renovate bot force-pushed the renovate/aws-cdk-monorepo branch 4 times, most recently from 3ba1bf4 to 2cc88b4 Compare October 24, 2020 01:08
@renovate renovate bot changed the title chore(deps): update aws-cdk monorepo to v1.69.0 chore(deps): update aws-cdk monorepo to v1.70.0 Oct 24, 2020
@renovate renovate bot force-pushed the renovate/aws-cdk-monorepo branch 7 times, most recently from 0ff7e76 to 5f903de Compare October 27, 2020 03:51
@renovate renovate bot force-pushed the renovate/aws-cdk-monorepo branch from c53b026 to dcc4b38 Compare April 1, 2021 09:03
@renovate renovate bot changed the title chore(deps): update aws-cdk monorepo to v1.95.1 chore(deps): update aws-cdk monorepo to v1.95.2 Apr 1, 2021
@renovate renovate bot force-pushed the renovate/aws-cdk-monorepo branch from dcc4b38 to 7307633 Compare April 1, 2021 16:02
@renovate renovate bot changed the title chore(deps): update aws-cdk monorepo to v1.95.2 chore(deps): update aws-cdk monorepo to v1.96.0 Apr 1, 2021
@renovate renovate bot force-pushed the renovate/aws-cdk-monorepo branch 7 times, most recently from ef851ec to b7fda3a Compare April 6, 2021 16:53
@renovate renovate bot changed the title chore(deps): update aws-cdk monorepo to v1.96.0 chore(deps): update aws-cdk monorepo to v1.97.0 Apr 6, 2021
@renovate renovate bot force-pushed the renovate/aws-cdk-monorepo branch 6 times, most recently from 7cca8c6 to 8b86302 Compare April 12, 2021 12:05
@renovate renovate bot changed the title chore(deps): update aws-cdk monorepo to v1.97.0 chore(deps): update aws-cdk monorepo to v1.98.0 Apr 12, 2021
@renovate renovate bot force-pushed the renovate/aws-cdk-monorepo branch 2 times, most recently from 503874e to 9aac083 Compare April 15, 2021 03:30
@renovate renovate bot force-pushed the renovate/aws-cdk-monorepo branch from 9aac083 to b1d172a Compare April 15, 2021 03:32
@henrist henrist merged commit 0e90524 into master Apr 15, 2021
@renovate renovate bot deleted the renovate/aws-cdk-monorepo branch April 15, 2021 03:52
@github-actions
Copy link

🎉 This PR is included in version 1.0.28 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants