Finalize release notes for v9.0.5 release (#132718)

* Finalize docs for v9.0.5 release

docs/release-notes/breaking-changes.md

@@ -18,7 +18,7 @@ There are no breaking changes associated with this release.
 
 ## 9.1.1 [elasticsearch-9.1.1-breaking-changes]
 
-There are no breaking changes associated with this release.
+No breaking changes in this version.
 
 ## 9.1.0 [elasticsearch-9.1.0-breaking-changes]
 
@@ -126,7 +126,7 @@ For more information, view [#126843](https://github.com/elastic/elasticsearch/pu
 
 ## 9.0.5 [elasticsearch-9.0.5-breaking-changes]
 
-There are no breaking changes associated with this release.
+No breaking changes in this version.
 
 ## 9.0.4 [elasticsearch-9.0.4-breaking-changes]
 

docs/release-notes/changelog-bundles/9.0.5.yml

@@ -1,6 +1,6 @@
 version: 9.0.5
-released: false
-generated: 2025-08-11T18:17:36.232343699Z
+released: true
+generated: 2025-08-12T11:34:40.403028310Z
 changelogs:
   - pr: 124918
     summary: Fix EQL double invoking listener

docs/release-notes/changelog-bundles/9.1.0.yml

@@ -669,6 +669,11 @@ changelogs:
     area: Machine Learning
     type: enhancement
     issues: []
+  - pr: 2831
+    summary: Track memory used in the hierarchical results normalizer
+    area: Machine Learning
+    type: enhancement
+    issues: []
   - pr: 125520
     summary: Add `FailedShardEntry` info to shard-failed task source string
     area: Allocation
@@ -1060,7 +1065,7 @@ changelogs:
       notable: true
       title: Upgrade `repository-s3` to AWS SDK v2
       body: |-
-        In earlier versions of {es} the `repository-s3` plugin was based on the AWS SDK v1. AWS will withdraw support for this SDK before the end of the life of {es} {minor-version} so we have migrated this plugin to the newer AWS SDK v2.
+        In earlier versions of {{es}} the `repository-s3` plugin was based on the AWS SDK v1. AWS will withdraw support for this SDK before the end of the life of {{es}} 9.1 so we have migrated this plugin to the newer AWS SDK v2.
         The two SDKs are not quite compatible, so please check the breaking changes documentation and test the new version thoroughly before upgrading any production workloads.
       pr: 126843
   - pr: 126856
@@ -1119,8 +1124,7 @@ changelogs:
         new data streams by specifying it in the new `data_stream_options` field
         inside of a component or index template:
 
-        [source,yaml]
-        ----
+        ```yaml
         PUT _index_template/my-template
         {
           "index_patterns": ["logs-test-*"],
@@ -1132,21 +1136,20 @@ changelogs:
               }
             }
           }
-        }'
-        ----
+        }
+        ```
 
         Existing data streams can be configured with the new data stream
         `_options` endpoint:
 
-        [source,yaml]
-        ----
+        ```yaml
         PUT _data_stream/logs-test-apache/_options
         {
           "failure_store": {
             "enabled": "true"
           }
         }
-        ----
+        ```
 
         When redirection is enabled, any ingestion related failures will be
         captured in the failure store if the cluster is able to, along with the
@@ -1158,18 +1161,16 @@ changelogs:
         stream data. In order to retrieve the failures, we use the `_search` API
         along with a new bit of index pattern syntax, the `::` selector.
 
-        [source,yaml]
-        ----
+        ```yaml
         POST logs-test-apache::failures/_search
-        ----
+        ```
 
         This index syntax informs the search operation to target the indices in
         its failure store instead of its backing indices. It can be mixed in a
         number of ways with other index patterns to include their failure store
         indices in the search operation:
 
-        [source,yaml]
-        ----
+        ```yaml
         POST logs-*::failures/_search
         POST logs-*,logs-*::failures/_search
         POST *::failures/_search
@@ -1177,7 +1178,7 @@ changelogs:
         {
           "query": "FROM my_data_stream*::failures"
         }
-        ----
+        ```
       pr: 126973
   - pr: 127006
     summary: Correctly handle non-integers in nested paths in the remove processor
@@ -1887,24 +1888,22 @@ changelogs:
 
         Example:
 
-        [source,yaml]
-        ----------------------------
+        ```yaml
         FROM test
         | FORK
         ( WHERE content:"fox" )
         ( WHERE content:"dog" )
         | SORT _fork
-        ----------------------------
+        ```
 
         The FORK command add a discriminator column called `_fork`:
 
-        [source,yaml]
-        ----------------------------
+        ```yaml
         | id  | content   | _fork |
         |-----|-----------|-------|
         | 3   | brown fox | fork1 |
         | 4   | white dog | fork2 |
-        ----------------------------
+        ```
       pr: 129606
   - pr: 129647
     summary: Fix `PushQueriesIT.testLike()` fails

docs/release-notes/deprecations.md

@@ -22,11 +22,15 @@ There are no deprecations associated with this release.
 
 ## 9.1.1 [elasticsearch-9.1.1-deprecations]
 
-There are no deprecations associated with this release.
+No deprecations in this version.
 
 ## 9.1.0 [elasticsearch-9.1.0-deprecations]
 
-There are no deprecations associated with this release.
+No deprecations in this version.
+
+## 9.0.5 [elasticsearch-9.0.5-deprecations]
+
+No deprecations in this version.
 
 ## 9.0.5 [elasticsearch-9.0.5-deprecations]
 

docs/release-notes/index.md

@@ -288,7 +288,6 @@ The FORK command add a discriminator column called `_fork`:
 | 3   | brown fox | fork1 |
 | 4   | white dog | fork2 |
 ```
-
 ::::
 
 ::::{dropdown} ES|QL cross-cluster querying is now generally available