chore(release): 1.5.2 [skip ci]

## [1.5.2](1.5.1...1.5.2) (2023-12-04)

### Bug Fixes

* Allow apigateways outside of eu-central-1 ([11efb67](11efb67)), closes [#64](#64)

CHANGELOG.md

@@ -1,3 +1,10 @@
+## [1.5.2](https://github.com/timo-reymann/terraform-module-aws-apigateway-swagger-ui/compare/1.5.1...1.5.2) (2023-12-04)
+
+
+### Bug Fixes
+
+* Allow apigateways outside of eu-central-1 ([11efb67](https://github.com/timo-reymann/terraform-module-aws-apigateway-swagger-ui/commit/11efb671d776eb314460dd14e70ee627bb55ae6b)), closes [#64](https://github.com/timo-reymann/terraform-module-aws-apigateway-swagger-ui/issues/64)
+
 ## [1.5.1](https://github.com/timo-reymann/terraform-module-aws-apigateway-swagger-ui/compare/1.5.0...1.5.1) (2023-09-20)
 
 

README.md

@@ -17,7 +17,7 @@ Serve Swagger documentation right from your API-Gateway.
 ```hcl
 module "swagger_ui" {
   source  = "timo-reymann/terraform-module-aws-apigateway-swagger-ui"
-  version = "1.5.1"
+  version = "1.5.2"
 
   prefix                     = "my-api-service"
   openapi_definition_content = file("my-definition.yml")
@@ -38,7 +38,7 @@ You can also reuse the output `routes` to get a reference or even generate it in
 ```hcl
 module "swagger_ui" {
   source  = "timo-reymann/terraform-module-aws-apigateway-swagger-ui"
-  version = "1.5.1"
+  version = "1.5.2"
 
   prefix                     = "my-api-service"
   openapi_definition_content = file("my-definition.yml")