docs: vmanomaly - release notes v1.15.[6-9] (#6879)

### Describe Your Changes

release notes for patches 1.15.6 - 9

### Checklist

The following checks are **mandatory**:

- [ ] My change adheres [VictoriaMetrics contributing
guidelines](https://docs.victoriametrics.com/contributing/).

docs/anomaly-detection/CHANGELOG.md

@@ -13,8 +13,25 @@ Please find the changelog for VictoriaMetrics Anomaly Detection below.
 
 > **Important note: Users are strongly encouraged to upgrade to `vmanomaly` [v1.9.2](https://hub.docker.com/repository/docker/victoriametrics/vmanomaly/tags?page=1&ordering=name) or newer for optimal performance and accuracy. <br><br> This recommendation is crucial for configurations with a low `infer_every` parameter [in your scheduler](https://docs.victoriametrics.com/anomaly-detection/components/scheduler/#parameters-1), and in scenarios where data exhibits significant high-order seasonality patterns (such as hourly or daily cycles). Previous versions from v1.5.1 to v1.8.0 were identified to contain a critical issue impacting model training, where models were inadvertently trained on limited data subsets, leading to suboptimal fits, affecting the accuracy of anomaly detection. <br><br> Upgrading to v1.9.2 addresses this issue, ensuring proper model training and enhanced reliability. For users utilizing Helm charts, it is recommended to upgrade to version [1.0.0](https://github.com/VictoriaMetrics/helm-charts/blob/master/charts/victoria-metrics-anomaly/CHANGELOG.md#100) or newer.**
 
+## v1.15.9
+Released: 2024-08-27
+- IMPROVEMENT: Added support for bearer token authentication in `push` mode within the [self-monitoring configuration section](https://docs.victoriametrics.com/anomaly-detection/components/monitoring/#push-config-parameters).
+
+## v1.15.8
+Released: 2024-08-27
+- FIX: Made minor adjustments to how the [reader](https://docs.victoriametrics.com/anomaly-detection/components/reader/#vm-reader) and [writer](https://docs.victoriametrics.com/anomaly-detection/components/writer/#vm-writer) handle bearer tokens across different modes.
+
+## v1.15.7
+Released: 2024-08-27
+- FIX: Made minor adjustments to how the [reader](https://docs.victoriametrics.com/anomaly-detection/components/reader/#vm-reader) and [writer](https://docs.victoriametrics.com/anomaly-detection/components/writer/#vm-writer) handle bearer tokens across different modes.
+
+## v1.15.6
+Released: 2024-08-26
+- IMPROVEMENT: Introduced the `bearer_token_file` argument to the [reader](https://docs.victoriametrics.com/anomaly-detection/components/reader/#vm-reader) and [writer](https://docs.victoriametrics.com/anomaly-detection/components/writer/#vm-writer) components to enhance secret management.
+
+
 ## v1.15.5
-Released: 2025-08-19
+Released: 2024-08-19
 - FIX: following [v1.15.2](https://docs.victoriametrics.com/anomaly-detection/changelog/#v1152) online model enhancement, now `data_range` parameter is correctly initialized for online models, created (for new time series returned by particular query) during `infer` calls. 
 
 ## v1.15.4

docs/anomaly-detection/components/monitoring.md

@@ -112,6 +112,28 @@ Deprecated since [v1.8.0](https://docs.victoriametrics.com/anomaly-detection/cha
         </tr>
         <tr>
             <td>
+`bearer_token`
+            </td>
+            <td>
+`token`
+            </td>
+            <td>
+Token is passed in the standard format with header: `Authorization: bearer {token}`. Available since [v1.15.9](https://docs.victoriametrics.com/anomaly-detection/changelog/#v1159)
+            </td>
+        </tr>
+        <tr>
+            <td>
+`bearer_token_file`
+            </td>
+            <td>
+`path_to_file`
+            </td>
+            <td>
+Path to a file, which contains token, that is passed in the standard format with header: `Authorization: bearer {token}`. Available since [v1.15.9](https://docs.victoriametrics.com/anomaly-detection/changelog/#v1159)
+            </td>
+        </tr>
+        <tr>
+            <td>
 
 `verify_tls`
             </td>

docs/anomaly-detection/components/reader.md

@@ -227,6 +227,17 @@ Token is passed in the standard format with header: `Authorization: bearer {toke
         </tr>
         <tr>
             <td>
+`bearer_token_file`
+            </td>
+            <td>
+`path_to_file`
+            </td>
+            <td>
+Path to a file, which contains token, that is passed in the standard format with header: `Authorization: bearer {token}`. Available since [v1.15.9](https://docs.victoriametrics.com/anomaly-detection/changelog/#v1159)
+            </td>
+        </tr>
+        <tr>
+            <td>
 `extra_filters`
             </td>
             <td>

docs/anomaly-detection/components/writer.md

@@ -199,16 +199,24 @@ Allows disabling TLS verification of the remote certificate.
         </tr>
         <tr>
             <td>
-
 `bearer_token`
             </td>
             <td>
-
 `token`
             </td>
             <td>
-
-Token is passed in the standard format with the header: `Authorization: bearer {token}`
+Token is passed in the standard format with header: `Authorization: bearer {token}`
+            </td>
+        </tr>
+        <tr>
+            <td>
+`bearer_token_file`
+            </td>
+            <td>
+`path_to_file`
+            </td>
+            <td>
+Path to a file, which contains token, that is passed in the standard format with header: `Authorization: bearer {token}`. Available since [v1.15.9](https://docs.victoriametrics.com/anomaly-detection/changelog/#v1159)
             </td>
         </tr>
     </tbody>