Skip to content

Commit

Permalink
chore(main): Release transformation-aws-compliance-premium v1.10.1 (#841
Browse files Browse the repository at this point in the history
)
  • Loading branch information
cq-bot authored May 6, 2024
1 parent 767a12f commit 2884c4d
Show file tree
Hide file tree
Showing 3 changed files with 9 additions and 2 deletions.
2 changes: 1 addition & 1 deletion .release-please-manifest.json
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@
"transformations/aws/data-resilience+FILLER": "0.0.0",
"transformations/aws/compliance-free": "1.4.0",
"transformations/aws/compliance-free+FILLER": "0.0.0",
"transformations/aws/compliance-premium": "1.10.0",
"transformations/aws/compliance-premium": "1.10.1",
"transformations/aws/compliance-premium+FILLER": "0.0.0",
"transformations/azure/compliance-free": "1.6.2",
"transformations/azure/compliance-free+FILLER": "0.0.0",
Expand Down
7 changes: 7 additions & 0 deletions transformations/aws/compliance-premium/CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,12 @@
# Changelog

## [1.10.1](https://github.com/cloudquery/policies-premium/compare/transformation-aws-compliance-premium-v1.10.0...transformation-aws-compliance-premium-v1.10.1) (2024-05-06)


### Bug Fixes

* Updated table aws_kms_key_rotation_statuses in vars ([#840](https://github.com/cloudquery/policies-premium/issues/840)) ([767a12f](https://github.com/cloudquery/policies-premium/commit/767a12f354e55634b966e853efdfe1ce0a9e95cb))

## [1.10.0](https://github.com/cloudquery/policies-premium/compare/transformation-aws-compliance-premium-v1.9.1...transformation-aws-compliance-premium-v1.10.0) (2024-05-06)


Expand Down
2 changes: 1 addition & 1 deletion transformations/aws/compliance-premium/dbt_project.yml
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
name: aws_compliance
version: 1.10.0
version: 1.10.1
config-version: 2
profile: aws_compliance
model-paths:
Expand Down

0 comments on commit 2884c4d

Please sign in to comment.