Skip to content

Conversation

@cq-bot
Copy link
Contributor

@cq-bot cq-bot commented Jul 19, 2023

🤖 I have created a release beep boop

22.0.0 (2023-07-20)

⚠ BREAKING CHANGES

  • aws: Define composite primary key for regions (#12415)
  • aws: Define primary key for s3_bucket_encryption_rules (#12408)
  • aws: Define primary key for dynamodb_table_continuous_backups (#12409)
  • aws: Define composite primary key for lambda_function_versions (#12402)

This Release has the Following Changes to Tables

  • Table aws_appconfig_deployment_strategies was added
  • Table aws_dynamodb_table_continuous_backups: primary key constraint added to column table_arn (:warning: breaking)
  • Table aws_dynamodb_table_continuous_backups: primary key constraint removed from column _cq_id (:warning: breaking)
  • Table aws_lambda_function_versions: primary key constraint added to column function_arn (:warning: breaking)
  • Table aws_lambda_function_versions: primary key constraint added to column version (:warning: breaking)
  • Table aws_lambda_function_versions: primary key constraint removed from column _cq_id (:warning: breaking)
  • Table aws_regions: primary key constraint added to column account_id (:warning: breaking)
  • Table aws_regions: primary key constraint added to column region (:warning: breaking)
  • Table aws_regions: primary key constraint removed from column _cq_id (:warning: breaking)
  • Table aws_s3_bucket_encryption_rules: primary key constraint added to column bucket_arn (:warning: breaking)
  • Table aws_s3_bucket_encryption_rules: primary key constraint removed from column _cq_id (:warning: breaking)

Features

  • aws: Define composite primary key for lambda_function_versions (#12402) (d1add18)
  • aws: Define composite primary key for regions (#12415) (681ea97)
  • aws: Define primary key for dynamodb_table_continuous_backups (#12409) (7d4a657)
  • aws: Define primary key for s3_bucket_encryption_rules (#12408) (a026b98)

Bug Fixes

  • sync: Pass DeterministicCQID option to scheduler (#12424) (eaac2e6)
  • Use correct name for DeploymentStrategies table (#12428) (dda4205)

This PR was generated with Release Please. See documentation.

@cq-bot cq-bot force-pushed the release-please--branches--main--components--plugins-source-aws branch 14 times, most recently from 34e471a to 82164d7 Compare July 20, 2023 12:00
@erezrokah erezrokah added the automerge Automatically merge once required checks pass label Jul 20, 2023
@cq-bot cq-bot force-pushed the release-please--branches--main--components--plugins-source-aws branch from b36ce03 to bdaa229 Compare July 20, 2023 12:03
@erezrokah erezrokah removed the automerge Automatically merge once required checks pass label Jul 20, 2023
@cq-bot cq-bot force-pushed the release-please--branches--main--components--plugins-source-aws branch 2 times, most recently from 8383e15 to 95e74a9 Compare July 20, 2023 12:16
@cq-bot cq-bot force-pushed the release-please--branches--main--components--plugins-source-aws branch from 1249abe to 858ad73 Compare July 20, 2023 12:23
@erezrokah erezrokah added the automerge Automatically merge once required checks pass label Jul 20, 2023
@kodiakhq kodiakhq bot merged commit e67c126 into main Jul 20, 2023
@kodiakhq kodiakhq bot deleted the release-please--branches--main--components--plugins-source-aws branch July 20, 2023 12:29
@cq-bot
Copy link
Contributor Author

cq-bot commented Jul 20, 2023

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

Labels

automerge Automatically merge once required checks pass

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants