describe the new 0.6.15 apif release (#75)

wallarm · Jan 29, 2024 · 41a00d2 · 41a00d2
1 parent 9d9d71e
commit 41a00d2
Show file tree

Hide file tree

Showing 4 changed files with 12 additions and 5 deletions.
diff --git a/docs/installation-guides/api-mode.md b/docs/installation-guides/api-mode.md
@@ -23,7 +23,7 @@ Use the following command to run the API Firewall container:
 
 ```
 docker run --rm -it -v <PATH_TO_SQLITE_DATABASE>:/var/lib/wallarm-api/1/wallarm_api.db \
-    -e APIFW_MODE=API -p 8282:8282 wallarm/api-firewall:v0.6.14
+    -e APIFW_MODE=API -p 8282:8282 wallarm/api-firewall:v0.6.15
 ```
 
 You can pass to the container the following variables:

diff --git a/docs/installation-guides/docker-container.md b/docs/installation-guides/docker-container.md
@@ -27,7 +27,7 @@ networks:
 services:
   api-firewall:
     container_name: api-firewall
-    image: wallarm/api-firewall:v0.6.14
+    image: wallarm/api-firewall:v0.6.15
     restart: on-failure
     volumes:
       - <HOST_PATH_TO_SPEC>:<CONTAINER_PATH_TO_SPEC>
@@ -153,6 +153,6 @@ To start API Firewall on Docker, you can also use regular Docker commands as in
         -v <HOST_PATH_TO_SPEC>:<CONTAINER_PATH_TO_SPEC> -e APIFW_API_SPECS=<PATH_TO_MOUNTED_SPEC> \
         -e APIFW_URL=<API_FIREWALL_URL> -e APIFW_SERVER_URL=<PROTECTED_APP_URL> \
         -e APIFW_REQUEST_VALIDATION=<REQUEST_VALIDATION_MODE> -e APIFW_RESPONSE_VALIDATION=<RESPONSE_VALIDATION_MODE> \
-        -p 8088:8088 wallarm/api-firewall:v0.6.14
+        -p 8088:8088 wallarm/api-firewall:v0.6.15
     ```
 4. When the environment is started, test it and enable traffic on API Firewall following steps 6 and 7.
diff --git a/docs/installation-guides/graphql/docker-container.md b/docs/installation-guides/graphql/docker-container.md
@@ -29,7 +29,7 @@ networks:
 services:
   api-firewall:
     container_name: api-firewall
-    image: wallarm/api-firewall:v0.6.14
+    image: wallarm/api-firewall:v0.6.15
     restart: on-failure
     volumes:
       - <HOST_PATH_TO_SPEC>:<CONTAINER_PATH_TO_SPEC>
@@ -184,6 +184,6 @@ To start API Firewall on Docker, you can also use regular Docker commands as in
         -e APIFW_GRAPHQL_MAX_QUERY_COMPLEXITY=<MAX_QUERY_COMPLEXITY> \
         -e APIFW_GRAPHQL_MAX_QUERY_DEPTH=<MAX_QUERY_DEPTH> -e APIFW_GRAPHQL_NODE_COUNT_LIMIT=<NODE_COUNT_LIMIT> \
         -e APIFW_GRAPHQL_INTROSPECTION=<ALLOW_INTROSPECTION_OR_NOT> \
-        -p 8088:8088 wallarm/api-firewall:v0.6.14
+        -p 8088:8088 wallarm/api-firewall:v0.6.15
     ```
 4. When the environment is started, test it and enable traffic on API Firewall following steps 6 and 7.
diff --git a/docs/release-notes.md b/docs/release-notes.md
@@ -2,6 +2,13 @@
 
 This page describes new releases of Wallarm API Firewall.
 
+## v0.6.15 (2023-12-21)
+
+* Dependency upgrade
+* Bug fixes
+* Add tests
+* When operating in the [`api` mode](installation-guides/api-mode.md), the API Firewall now returns error messages in responses for requests containing parameter values that exceed the minimum and maximum limits defined in the OpenAPI specification
+
 ## v0.6.14 (2023-11-23)
 
 * Introduced new environment variables to limit GraphQL queries: `APIFW_GRAPHQL_MAX_ALIASES_NUM` and `APIFW_GRAPHQL_FIELD_DUPLICATION`.