Update Elasticsearch release notes automation (#132930)

* Update breaking changes and deprecations

* update release note tagging

* revert tagging change

* Update tests after template changes

* [docs] Add support for overriding entries in the release notes (#133592)

* [docs] Add support for overriding entries in the release notes

* Update changelog bundles with overrides

* Use ga instead of comming tag

* Update tests after template change

---------

Co-authored-by: Brian Seeders <brian.seeders@elastic.co>

build-tools-internal/src/main/java/org/elasticsearch/gradle/internal/release/ChangelogEntry.java

@@ -43,6 +43,7 @@ public class ChangelogEntry {
     private Breaking breaking;
     private Highlight highlight;
     private Deprecation deprecation;
+    private String entryOverride;
 
     private static final ObjectMapper yamlMapper = new ObjectMapper(new YAMLFactory());
 
@@ -125,6 +126,14 @@ public class ChangelogEntry {
         this.deprecation = deprecation;
     }
 
+    public String getEntryOverride() {
+        return entryOverride;
+    }
+
+    public void setEntryOverride(String entryOverride) {
+        this.entryOverride = entryOverride;
+    }
+
     @Override
     public boolean equals(Object o) {
         if (this == o) {
@@ -140,12 +149,13 @@ public class ChangelogEntry {
             && Objects.equals(type, that.type)
             && Objects.equals(summary, that.summary)
             && Objects.equals(highlight, that.highlight)
-            && Objects.equals(breaking, that.breaking);
+            && Objects.equals(breaking, that.breaking)
+            && Objects.equals(entryOverride, that.entryOverride);
     }
 
     @Override
     public int hashCode() {
-        return Objects.hash(pr, issues, area, type, summary, highlight, breaking);
+        return Objects.hash(pr, issues, area, type, summary, highlight, breaking, entryOverride);
     }
 
     @Override

build-tools-internal/src/main/resources/templates/breaking-changes.md

@@ -22,29 +22,35 @@ for(bundle in changelogBundles) {
     if (coming) {
         print "\n"
         print "```{applies_to}\n"
-        print "stack: coming ${version}\n"
+        print "stack: ga ${version}\n"
         print "```"
     }
 %>
 ## ${unqualifiedVersion} [elasticsearch-${versionForIds}-breaking-changes]
+
 <%
     if (!changelogsByTypeByArea['breaking']) {
-        print "\nNo breaking changes in this version.\n"
+        print "There are no breaking changes associated with this release.\n"
     } else {
         for (team in (changelogsByTypeByArea['breaking'] ?: [:]).keySet()) {
-            print "\n${team}:\n";
+            print "${team}:\n";
 
             for (change in changelogsByTypeByArea['breaking'][team]) {
-                print "* ${change.summary} [#${change.pr}](https://github.com/elastic/elasticsearch/pull/${change.pr})"
-                if (change.issues != null && change.issues.empty == false) {
-                    print change.issues.size() == 1 ? " (issue: " : " (issues: "
-                    print change.issues.collect { "[#${it}](https://github.com/elastic/elasticsearch/issues/${it})" }.join(", ")
-                    print ")"
+                if (!change.entryOverride) {
+                    print "* ${change.summary} [#${change.pr}](https://github.com/elastic/elasticsearch/pull/${change.pr})"
+                    if (change.issues != null && change.issues.empty == false) {
+                        print change.issues.size() == 1 ? " (issue: " : " (issues: "
+                        print change.issues.collect { "[#${it}](https://github.com/elastic/elasticsearch/issues/${it})" }.join(", ")
+                        print ")"
+                    }
+                } else {
+                    print change.entryOverride;
                 }
                 print "\n"
             }
+            print "\n"
         }
 
-        print "\n\n"
+        print "\n"
     }
 }

build-tools-internal/src/main/resources/templates/deprecations.md

@@ -26,14 +26,14 @@ for(bundle in changelogBundles) {
     if (coming) {
         print "\n"
         print "```{applies_to}\n"
-        print "stack: coming ${version}\n"
+        print "stack: ga ${version}\n"
         print "```"
     }
 %>
 ## ${unqualifiedVersion} [elasticsearch-${versionForIds}-deprecations]
 <%
     if (!changelogsByTypeByArea['deprecation']) {
-        print "\nNo deprecations in this version.\n"
+        print "\nThere are no deprecations associated with this release.\n"
     } else {
         for (team in (changelogsByTypeByArea['deprecation'] ?: [:]).keySet()) {
             print "\n${team}:\n";

build-tools-internal/src/main/resources/templates/index.md

@@ -34,7 +34,7 @@ for(bundle in changelogBundles) {
 
 if (coming) {
     print "```{applies_to}\n"
-    print "stack: coming ${version}\n"
+    print "stack: ga ${version}\n"
     print "```"
     print "\n"
 }
@@ -59,18 +59,24 @@ for (changeType in ['features-enhancements', 'fixes', 'regression']) {
     }
 %>
 ### ${ TYPE_LABELS.getOrDefault(changeType, 'No mapping for TYPE_LABELS[' + changeType + ']') } [elasticsearch-${versionForIds}-${changeType}]
+
 <% for (team in changelogsByTypeByArea[changeType].keySet()) {
-    print "\n${team}:\n";
+    print "${team}:\n";
 
     for (change in changelogsByTypeByArea[changeType][team]) {
-        print "* ${change.summary} [#${change.pr}](https://github.com/elastic/elasticsearch/pull/${change.pr})"
-        if (change.issues != null && change.issues.empty == false) {
-            print change.issues.size() == 1 ? " (issue: " : " (issues: "
-            print change.issues.collect { "[#${it}](https://github.com/elastic/elasticsearch/issues/${it})" }.join(", ")
-            print ")"
+        if (!change.entryOverride) {
+            print "* ${change.summary} [#${change.pr}](https://github.com/elastic/elasticsearch/pull/${change.pr})"
+            if (change.issues != null && change.issues.empty == false) {
+                print change.issues.size() == 1 ? " (issue: " : " (issues: "
+                print change.issues.collect { "[#${it}](https://github.com/elastic/elasticsearch/issues/${it})" }.join(", ")
+                print ")"
+            }
+        } else {
+            print change.entryOverride.trim();
         }
         print "\n"
     }
+    print "\n"
 }
 }
 print "\n"

build-tools-internal/src/test/resources/org/elasticsearch/gradle/internal/release/ReleaseNotesGeneratorTest.breaking-changes.md

@@ -13,54 +13,54 @@ If you are migrating from a version prior to version 9.0, you must first upgrade
 % ## Next version [elasticsearch-nextversion-breaking-changes]
 
 ```{applies_to}
-stack: coming 9.1.0
+stack: ga 9.1.0
 ```
 ## 9.1.0 [elasticsearch-9.1.0-breaking-changes]
 
-No breaking changes in this version.
+There are no breaking changes associated with this release.
 
 ```{applies_to}
-stack: coming 9.0.10
+stack: ga 9.0.10
 ```
 ## 9.0.10 [elasticsearch-9.0.10-breaking-changes]
 
-No breaking changes in this version.
+There are no breaking changes associated with this release.
 
 ## 9.0.9 [elasticsearch-9.0.9-breaking-changes]
 
-No breaking changes in this version.
+There are no breaking changes associated with this release.
 
 ## 9.0.8 [elasticsearch-9.0.8-breaking-changes]
 
-No breaking changes in this version.
+There are no breaking changes associated with this release.
 
 ## 9.0.7 [elasticsearch-9.0.7-breaking-changes]
 
-No breaking changes in this version.
+There are no breaking changes associated with this release.
 
 ## 9.0.6 [elasticsearch-9.0.6-breaking-changes]
 
-No breaking changes in this version.
+There are no breaking changes associated with this release.
 
 ## 9.0.5 [elasticsearch-9.0.5-breaking-changes]
 
-No breaking changes in this version.
+There are no breaking changes associated with this release.
 
 ## 9.0.4 [elasticsearch-9.0.4-breaking-changes]
 
-No breaking changes in this version.
+There are no breaking changes associated with this release.
 
 ## 9.0.3 [elasticsearch-9.0.3-breaking-changes]
 
-No breaking changes in this version.
+There are no breaking changes associated with this release.
 
 ## 9.0.2 [elasticsearch-9.0.2-breaking-changes]
 
-No breaking changes in this version.
+There are no breaking changes associated with this release.
 
 ## 9.0.1 [elasticsearch-9.0.1-breaking-changes]
 
-No breaking changes in this version.
+There are no breaking changes associated with this release.
 
 ## 9.0.0 [elasticsearch-900-breaking-changes]
 

build-tools-internal/src/test/resources/org/elasticsearch/gradle/internal/release/ReleaseNotesGeneratorTest.deprecations.md

@@ -17,38 +17,38 @@ To give you insight into what deprecated features you’re using, {{es}}:
 % ## Next version [elasticsearch-nextversion-deprecations]
 
 ```{applies_to}
-stack: coming 9.1.0
+stack: ga 9.1.0
 ```
 ## 9.1.0 [elasticsearch-9.1.0-deprecations]
 
-No deprecations in this version.
+There are no deprecations associated with this release.
 
 ```{applies_to}
-stack: coming 9.0.10
+stack: ga 9.0.10
 ```
 ## 9.0.10 [elasticsearch-9.0.10-deprecations]
 
-No deprecations in this version.
+There are no deprecations associated with this release.
 
 ## 9.0.9 [elasticsearch-9.0.9-deprecations]
 
-No deprecations in this version.
+There are no deprecations associated with this release.
 
 ## 9.0.8 [elasticsearch-9.0.8-deprecations]
 
-No deprecations in this version.
+There are no deprecations associated with this release.
 
 ## 9.0.7 [elasticsearch-9.0.7-deprecations]
 
-No deprecations in this version.
+There are no deprecations associated with this release.
 
 ## 9.0.6 [elasticsearch-9.0.6-deprecations]
 
-No deprecations in this version.
+There are no deprecations associated with this release.
 
 ## 9.0.5 [elasticsearch-9.0.5-deprecations]
 
-No deprecations in this version.
+There are no deprecations associated with this release.
 
 ## 9.0.4 [elasticsearch-9.0.4-deprecations]
 
@@ -60,16 +60,16 @@ Search:
 
 ## 9.0.3 [elasticsearch-9.0.3-deprecations]
 
-No deprecations in this version.
+There are no deprecations associated with this release.
 
 ## 9.0.2 [elasticsearch-9.0.2-deprecations]
 
-No deprecations in this version.
+There are no deprecations associated with this release.
 
 ## 9.0.1 [elasticsearch-9.0.1-deprecations]
 
-No deprecations in this version.
+There are no deprecations associated with this release.
 
 ## 9.0.0 [elasticsearch-900-deprecations]
 
-No deprecations in this version.
+There are no deprecations associated with this release.

build-tools-internal/src/test/resources/org/elasticsearch/gradle/internal/release/ReleaseNotesGeneratorTest.index.md

@@ -22,7 +22,7 @@ To check for security updates, go to [Security announcements for the Elastic sta
 
 ## 9.1.0 [elasticsearch-9.1.0-release-notes]
 ```{applies_to}
-stack: coming 9.1.0
+stack: ga 9.1.0
 ```
 
 ### Highlights [elasticsearch-9.1.0-highlights]
@@ -47,9 +47,10 @@ Search:
 *  [#52](https://github.com/elastic/elasticsearch/pull/52)
 
 
+
 ## 9.0.10 [elasticsearch-9.0.10-release-notes]
 ```{applies_to}
-stack: coming 9.0.10
+stack: ga 9.0.10
 ```
 
 ### Features and enhancements [elasticsearch-9.0.10-features-enhancements]
@@ -59,6 +60,7 @@ Search:
 * Test changelog entry 10_1 [#10002](https://github.com/elastic/elasticsearch/pull/10002) (issues: [#10003](https://github.com/elastic/elasticsearch/issues/10003), [#10004](https://github.com/elastic/elasticsearch/issues/10004))
 
 
+
 ## 9.0.9 [elasticsearch-9.0.9-release-notes]
 
 ### Regressions [elasticsearch-9.0.9-regression]
@@ -68,6 +70,7 @@ Mappings:
 * Test changelog entry 9_1 [#9002](https://github.com/elastic/elasticsearch/pull/9002) (issues: [#9003](https://github.com/elastic/elasticsearch/issues/9003), [#9004](https://github.com/elastic/elasticsearch/issues/9004))
 
 
+
 ## 9.0.8 [elasticsearch-9.0.8-release-notes]
 
 ### Features and enhancements [elasticsearch-9.0.8-features-enhancements]
@@ -77,6 +80,7 @@ Indices:
 * Test changelog entry 8_1 [#8002](https://github.com/elastic/elasticsearch/pull/8002) (issues: [#8003](https://github.com/elastic/elasticsearch/issues/8003), [#8004](https://github.com/elastic/elasticsearch/issues/8004))
 
 
+
 ## 9.0.7 [elasticsearch-9.0.7-release-notes]
 
 ### Features and enhancements [elasticsearch-9.0.7-features-enhancements]
@@ -86,6 +90,7 @@ Cluster:
 * Test changelog entry 7_1 [#7002](https://github.com/elastic/elasticsearch/pull/7002) (issues: [#7003](https://github.com/elastic/elasticsearch/issues/7003), [#7004](https://github.com/elastic/elasticsearch/issues/7004))
 
 
+
 ## 9.0.6 [elasticsearch-9.0.6-release-notes]
 
 ### Features and enhancements [elasticsearch-9.0.6-features-enhancements]
@@ -95,6 +100,7 @@ Aggregation:
 * Test changelog entry 6_1 [#6002](https://github.com/elastic/elasticsearch/pull/6002) (issues: [#6003](https://github.com/elastic/elasticsearch/issues/6003), [#6004](https://github.com/elastic/elasticsearch/issues/6004))
 
 
+
 ## 9.0.5 [elasticsearch-9.0.5-release-notes]
 
 ### Features and enhancements [elasticsearch-9.0.5-features-enhancements]
@@ -104,6 +110,7 @@ Security:
 * Test changelog entry 5_1 [#5002](https://github.com/elastic/elasticsearch/pull/5002) (issues: [#5003](https://github.com/elastic/elasticsearch/issues/5003), [#5004](https://github.com/elastic/elasticsearch/issues/5004))
 
 
+
 ## 9.0.4 [elasticsearch-9.0.4-release-notes]
 
 
@@ -116,6 +123,7 @@ Mappings:
 * Test changelog entry 3_1 [#3002](https://github.com/elastic/elasticsearch/pull/3002) (issues: [#3003](https://github.com/elastic/elasticsearch/issues/3003), [#3004](https://github.com/elastic/elasticsearch/issues/3004))
 
 
+
 ## 9.0.2 [elasticsearch-9.0.2-release-notes]
 
 ### Fixes [elasticsearch-9.0.2-fixes]
@@ -125,6 +133,7 @@ Indices:
 * Test changelog entry 2_1 [#2002](https://github.com/elastic/elasticsearch/pull/2002) (issues: [#2003](https://github.com/elastic/elasticsearch/issues/2003), [#2004](https://github.com/elastic/elasticsearch/issues/2004))
 
 
+
 ## 9.0.1 [elasticsearch-9.0.1-release-notes]
 
 

build-tools-internal/src/test/resources/org/elasticsearch/gradle/internal/release/ReleaseNotesGeneratorTest.index.no-highlights.md

@@ -22,7 +22,7 @@ To check for security updates, go to [Security announcements for the Elastic sta
 
 ## 9.0.10 [elasticsearch-9.0.10-release-notes]
 ```{applies_to}
-stack: coming 9.0.10
+stack: ga 9.0.10
 ```
 
 ### Features and enhancements [elasticsearch-9.0.10-features-enhancements]
@@ -32,6 +32,7 @@ Search:
 * Test changelog entry 10_1 [#10002](https://github.com/elastic/elasticsearch/pull/10002) (issues: [#10003](https://github.com/elastic/elasticsearch/issues/10003), [#10004](https://github.com/elastic/elasticsearch/issues/10004))
 
 
+
 ## 9.0.9 [elasticsearch-9.0.9-release-notes]
 
 ### Regressions [elasticsearch-9.0.9-regression]
@@ -41,6 +42,7 @@ Mappings:
 * Test changelog entry 9_1 [#9002](https://github.com/elastic/elasticsearch/pull/9002) (issues: [#9003](https://github.com/elastic/elasticsearch/issues/9003), [#9004](https://github.com/elastic/elasticsearch/issues/9004))
 
 
+
 ## 9.0.8 [elasticsearch-9.0.8-release-notes]
 
 ### Features and enhancements [elasticsearch-9.0.8-features-enhancements]
@@ -50,6 +52,7 @@ Indices:
 * Test changelog entry 8_1 [#8002](https://github.com/elastic/elasticsearch/pull/8002) (issues: [#8003](https://github.com/elastic/elasticsearch/issues/8003), [#8004](https://github.com/elastic/elasticsearch/issues/8004))
 
 
+
 ## 9.0.7 [elasticsearch-9.0.7-release-notes]
 
 ### Features and enhancements [elasticsearch-9.0.7-features-enhancements]
@@ -59,6 +62,7 @@ Cluster:
 * Test changelog entry 7_1 [#7002](https://github.com/elastic/elasticsearch/pull/7002) (issues: [#7003](https://github.com/elastic/elasticsearch/issues/7003), [#7004](https://github.com/elastic/elasticsearch/issues/7004))
 
 
+
 ## 9.0.6 [elasticsearch-9.0.6-release-notes]
 
 ### Features and enhancements [elasticsearch-9.0.6-features-enhancements]
@@ -68,6 +72,7 @@ Aggregation:
 * Test changelog entry 6_1 [#6002](https://github.com/elastic/elasticsearch/pull/6002) (issues: [#6003](https://github.com/elastic/elasticsearch/issues/6003), [#6004](https://github.com/elastic/elasticsearch/issues/6004))
 
 
+
 ## 9.0.5 [elasticsearch-9.0.5-release-notes]
 
 ### Features and enhancements [elasticsearch-9.0.5-features-enhancements]
@@ -77,6 +82,7 @@ Security:
 * Test changelog entry 5_1 [#5002](https://github.com/elastic/elasticsearch/pull/5002) (issues: [#5003](https://github.com/elastic/elasticsearch/issues/5003), [#5004](https://github.com/elastic/elasticsearch/issues/5004))
 
 
+
 ## 9.0.4 [elasticsearch-9.0.4-release-notes]
 
 
@@ -89,6 +95,7 @@ Mappings:
 * Test changelog entry 3_1 [#3002](https://github.com/elastic/elasticsearch/pull/3002) (issues: [#3003](https://github.com/elastic/elasticsearch/issues/3003), [#3004](https://github.com/elastic/elasticsearch/issues/3004))
 
 
+
 ## 9.0.2 [elasticsearch-9.0.2-release-notes]
 
 ### Fixes [elasticsearch-9.0.2-fixes]
@@ -98,6 +105,7 @@ Indices:
 * Test changelog entry 2_1 [#2002](https://github.com/elastic/elasticsearch/pull/2002) (issues: [#2003](https://github.com/elastic/elasticsearch/issues/2003), [#2004](https://github.com/elastic/elasticsearch/issues/2004))
 
 
+
 ## 9.0.1 [elasticsearch-9.0.1-release-notes]
 
 

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

@@ -7,60 +7,113 @@ changelogs:
     area: EQL
     type: bug
     issues: []
+    entryOverride: |
+      :::{dropdown} Prevent double invocation of EQL listener
+      In some cases, the EQL listener could be resolved twice, potentially leading to unexpected behavior.
+      [#124918](https://github.com/elastic/elasticsearch/pull/124918) updates the control flow to exit early and ensure the listener is only invoked once.
+      :::
   - pr: 129282
     summary: "Fix query rewrite logic to preserve `boosts` and `queryName` for `match`, `knn`, and `sparse_vector` queries on semantic_text fields"
     area: Search
     type: bug
     issues: []
+    entryOverride: |
+      :::{dropdown} Preserve `boost` and `queryName` for semantic queries
+      Query rewrite logic dropped `boost` and `queryName` values for `match`, `knn`, and `sparse_vector` queries on `semantic_text` fields, causing query weighting and naming to be lost. [#129282](https://github.com/elastic/elasticsearch/pull/129282) resolves the issue so these values are now preserved correctly during query rewriting.
+      :::
   - pr: 129745
     summary: "ESQL: Fix `mv_expand` inconsistent column order"
     area: ES|QL
     type: bug
     issues:
       - 129000
+    entryOverride: |
+      :::{dropdown} Fix `mv_expand` inconsistent column order
+      The `mv_expand` command could return columns in a different order depending on query execution paths. Now, the new attribute generated by `mv_expand` preserves the original field positions in the output. [#129745](https://github.com/elastic/elasticsearch/pull/129745) (issue: [#129000](https://github.com/elastic/elasticsearch/issues/129000))
+      :::
   - pr: 130279
     summary: Fix missing removal of query cancellation callback in QueryPhase
     area: Search
     type: bug
     issues:
       - 130071
+    entryOverride: |
+      :::{dropdown} Fix missing removal of query cancellation callback in QueryPhase
+      A missing removal of a query cancellation callback caused unintended timeouts or cancellations in later search phases when `allow_partial_search_results` was enabled, which could lead to `ArrayIndexOutOfBoundsException` errors.
+      [#130279](https://github.com/elastic/elasticsearch/pull/130279) resolves the issue and ensures predictable search execution. (issue: [#130071](https://github.com/elastic/elasticsearch/issues/130071))
+      :::
   - pr: 131236
     summary: Correctly handling `download_database_on_pipeline_creation` within a pipeline processor within a default or final pipeline
     area: Ingest Node
     type: bug
     issues: []
+    entryOverride: |
+      :::{dropdown} Correctly handle `download_database_on_pipeline_creation` in default or final pipelines
+      A bug in the `download_database_on_pipeline_creation` setting caused geoip databases not to download when the geoip processor was referenced from a pipeline processor in a default or final pipeline.
+      This resulted in documents being tagged with `_geoip_database_unavailable_GeoLite2-City.mmdb` instead of having geo data.
+      [#131236](https://github.com/elastic/elasticsearch/pull/131236) resolves the issue and ensures geoip databases download correctly in this scenario.
+      :::
   - pr: 131391
     summary: Fix bug in point in time response
     area: Search
     type: bug
     issues:
       - 131026
+    entryOverride: |
+      :::{dropdown} Correct shard status reporting in point-in-time responses
+      The Open PIT API incorrectly swapped the skipped and failed shard counts when partial search results were allowed. This caused the API to report failed shards as skipped and vice versa. [#131391](https://github.com/elastic/elasticsearch/pull/131391) fixes the field mapping so shard status is reported accurately. (issue: [#131026](https://github.com/elastic/elasticsearch/issues/131026))
+      :::
   - pr: 131426
     summary: Disallow remote enrich after lu join
     area: ES|QL
     type: bug
     issues:
       - 129372
+    entryOverride: |
+      :::{dropdown} Disallow remote `ENRICH` after `LOOKUP JOIN`
+      Combining a `LOOKUP JOIN` with remote `ENRICH` could trigger a `ClassCastException` due to pipeline breaker interactions when limits or top-N queries were involved. [#131426](https://github.com/elastic/elasticsearch/pull/131426) adds a validation that forbids remote `ENRICH` after `LOOKUP JOIN`, preventing the runtime error. (issue: [#129372](https://github.com/elastic/elasticsearch/issues/129372))
+      :::
   - pr: 131429
     summary: Prevent auto-sharding for data streams in LOOKUP index mode
     area: Data streams
     type: bug
     issues: []
+    entryOverride: |
+      :::{dropdown} Disables auto-sharding for LOOKUP index mode
+      Auto-sharding for data streams caused unsupported replica scaling when the index mode was set to `LOOKUP`.
+      This happened because lookup mappers do not support scaling beyond one replica.
+      [#131429](https://github.com/elastic/elasticsearch/pull/131429) resolves this issue by disabling auto-sharding for data streams with `LOOKUP` index modes, avoiding unsupported replica settings.
+      :::
   - pr: 131630
     summary: Fix memory usage estimation for ELSER models
     area: Machine Learning
     type: bug
     issues: []
+    entryOverride: |
+      :::{dropdown} Fix memory usage estimation for ELSER models
+      Using the deployment ID instead of the model ID caused `isElserV1Or2Model` to fail for ELSER models, because deployment IDs don’t start with `.elser_model_2`.
+      [#131630](https://github.com/elastic/elasticsearch/pull/131630) updates the code to pass the model ID, ensuring memory usage is estimated correctly.
+      :::
   - pr: 131677
     summary: Throw better exception if verifying empty repo
     area: Snapshot/Restore
     type: bug
     issues: []
+    entryOverride: |
+      :::{dropdown} Improve error handling when verifying an empty snapshot repository
+
+      Verifying the integrity of a brand-new snapshot repository without any index blobs failed with a low-level error because the repository generation was `-1`, which cannot be sent over the wire. [#131677](https://github.com/elastic/elasticsearch/pull/131677) updates the logic to reject such requests early with a clearer, more helpful error message.
+      :::
   - pr: 131680
     summary: Grant server module read/write entitlements for deprecated path setting "path.shared_data"
     area: Infra/Core
     type: bug
     issues: []
+    entryOverride: |
+      :::{dropdown} Grants server module read/write permissions for deprecated `path.shared_data` setting
+      The server module is now granted read/write permissions for the deprecated `path.shared_data` setting.
+      [#131680](https://github.com/elastic/elasticsearch/pull/131680) resolves issues surfaced in internal testing and ensures compatibility with legacy configurations.
+      :::
   - pr: 131711
     summary: Track & log when there is insufficient disk space available to execute merges
     area: Engine
@@ -71,31 +124,67 @@ changelogs:
     area: Machine Learning
     type: bug
     issues: []
+    entryOverride: |
+      :::{dropdown} Prevents double-counting of allocations in trained model deployment memory estimation
+      A recent refactor introduced a bug that caused the trained model memory estimation to double-count the number of allocations, leading to inflated memory usage projections.
+      [#131990](https://github.com/elastic/elasticsearch/pull/131990) resolves the issue by reverting the change and restoring accurate memory estimation for trained model deployments.
+      :::
   - pr: 132018
     summary: Fix decoding of non-ascii field names in ignored source
     area: Mapping
     type: bug
     issues: []
+    entryOverride: |
+      :::{dropdown} Fixes decoding failure for non-ASCII field names in `_ignored_source`
+      A decoding error occurred when field names in `_ignored_source` contained non-ASCII characters.
+      This happened because `String.length()` was used to calculate the byte length of the field name, which only works correctly for ASCII characters.
+      [#132018](https://github.com/elastic/elasticsearch/pull/132018) resolves the issue by using the actual byte array length of the encoded field name, ensuring proper decoding regardless of character encoding.
+      :::
   - pr: 132101
     summary: Simulate ingest API uses existing index mapping when `mapping_addition` is given
     area: Ingest Node
     type: bug
     issues: []
+    entryOverride: |
+      :::{dropdown} Fixes incorrect mapping resolution in simulate ingest API when `mapping_addition` is provided
+      When using the simulate ingest API with a `mapping_addition`, the system incorrectly ignored the existing mapping of the target index and instead applied the mapping from a matching index template, if one existed.
+      This caused mismatches between the index and simulation behavior.
+      [#132101](https://github.com/elastic/elasticsearch/pull/132101) resolves the issue and ensures that the index’s actual mapping is used when available, preserving consistency between simulation and execution.
+      :::
   - pr: 132167
     summary: Deal with internally created IN in a different way for EQL
     area: EQL
     type: bug
     issues:
       - 118621
+    entryOverride: |
+      :::{dropdown} Resolves EQL parsing failure for IP-mapped fields in `OR` expressions
+      Parsing EQL queries failed when comparing the same IP-mapped field to multiple values joined by an `OR` expression.
+      This occurred because lookup operators were internally rewritten into `IN` expressions, which are unsupported for IP-type fields.
+      [#132167](https://github.com/elastic/elasticsearch/pull/132167) resolves the issue and ensures EQL can now successfully parse and execute such or queries involving IP fields. (issue: [#118621](https://github.com/elastic/elasticsearch/issues/118621))
+      :::
   - pr: 132260
     summary: FIx Driver creating status with a live list of operators
     area: ES|QL
     type: bug
     issues:
       - 131564
+    entryOverride: |
+      :::{dropdown} Fixes `ConcurrentModificationException` caused by live operator list
+      A `ConcurrentModificationException` caused test failures in `CrossClusterAsyncEnrichStopIT.testEnrichAfterStop` under certain conditions.
+      This happened because the ES|QL driver added a live operator list to the `DriverStatus` object, which could be modified while the status was being serialized.
+      [#132260](https://github.com/elastic/elasticsearch/pull/132260) fixes the issue by copying the operator list before storing it, preventing concurrent changes during status reads.
+      (issue: [#131564](https://github.com/elastic/elasticsearch/issues/131564))
+      :::
   - pr: 132320
     summary: "Aggs: Add validation to Bucket script pipeline agg"
     area: Aggregations
     type: bug
     issues:
       - 132272
+    entryOverride: |
+      :::{dropdown} Validate parent aggregation type in `bucket_script`
+      The `bucket_script` pipeline aggregation didn’t validate that its parent aggregation was a multi-bucket aggregation.
+      This caused a `ClassCastException` at runtime when the parent was not multi-bucket.
+      [#132320](https://github.com/elastic/elasticsearch/pull/132320) adds a validation step so the aggregation fails early, preventing the runtime error. (issue: [#132272](https://github.com/elastic/elasticsearch/issues/132272))
+      :::

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

@@ -162,6 +162,26 @@ changelogs:
     area: Discovery-Plugins
     type: breaking
     issues: []
+    entryOverride: |
+      :::{dropdown} Migrates `discovery-ec2` plugin to AWS SDK v2
+      The `discovery-ec2` plugin now uses AWS SDK v2 instead of v1, as AWS plans to deprecate SDK v1 before the end of Elasticsearch 8.19’s support period. AWS SDK v2 introduces several behavior changes that affect configuration.
+
+      **Impact:**
+      If you use the `discovery-ec2` plugin, your existing settings may no longer be compatible. Notable changes include, but may not be limited to:
+      - AWS SDK v2 does not support the EC2 IMDSv1 protocol.
+      - AWS SDK v2 does not support the `aws.secretKey` or `com.amazonaws.sdk.ec2MetadataServiceEndpointOverride` system properties.
+      - AWS SDK v2 does not permit specifying a choice between HTTP and HTTPS so the `discovery.ec2.protocol` setting is no longer effective.
+      - AWS SDK v2 does not accept an access key without a secret key or vice versa.
+
+      **Action:**
+      Test the upgrade in a non-production environment. Adapt your configuration to the new SDK functionality. This includes, but may not be limited to, the following items:
+      - If you use IMDS to determine the availability zone of a node or to obtain credentials for accessing the EC2 API, ensure that it supports the IMDSv2 protocol.
+      - If applicable, discontinue use of the `aws.secretKey` and `com.amazonaws.sdk.ec2MetadataServiceEndpointOverride` system properties.
+      - If applicable, specify that you wish to use the insecure HTTP protocol to access the EC2 API by setting `discovery.ec2.endpoint` to a URL which starts with `http://`.
+      - Either supply both an access key and a secret key using the `discovery.ec2.access_key` and `discovery.ec2.secret_key` keystore settings, or configure neither of these settings.
+
+      For more information, view [#122062](https://github.com/elastic/elasticsearch/pull/122062).
+      :::
     breaking:
       area: Cluster and node setting
       title: Upgrade `discovery-ec2` to AWS SDK v2
@@ -246,7 +266,7 @@ changelogs:
     type: enhancement
     issues: []
   - pr: 122458
-    summary: '`DesiredBalanceReconciler` always returns `AllocationStats`'
+    summary: "`DesiredBalanceReconciler` always returns `AllocationStats`"
     area: Allocation
     type: bug
     issues: []
@@ -483,7 +503,7 @@ changelogs:
     type: enhancement
     issues: []
   - pr: 124595
-    summary: '`ToAggregateMetricDouble` function'
+    summary: "`ToAggregateMetricDouble` function"
     area: ES|QL
     type: enhancement
     issues: []
@@ -801,7 +821,7 @@ changelogs:
     type: enhancement
     issues: []
   - pr: 126264
-    summary: '`FileWatchingService` shoudld not throw for missing file'
+    summary: "`FileWatchingService` shoudld not throw for missing file"
     area: Infra/Settings
     type: enhancement
     issues: []
@@ -900,7 +920,7 @@ changelogs:
     type: bug
     issues: []
   - pr: 126581
-    summary: 'Optimize shared blob cache evictions on shard removal Shared blob cache evictions occur on the cluster applier thread when shards are removed from a node. These can be expensive if a large number of shards are being removed. This change uses the context of the removal to avoid unnecessary evictions that might hold up the applier thread. '
+    summary: "Optimize shared blob cache evictions on shard removal Shared blob cache evictions occur on the cluster applier thread when shards are removed from a node. These can be expensive if a large number of shards are being removed. This change uses the context of the removal to avoid unnecessary evictions that might hold up the applier thread. "
     area: Snapshot/Restore
     type: enhancement
     issues: []
@@ -1004,6 +1024,32 @@ changelogs:
     type: breaking
     issues:
       - 120993
+    entryOverride: |
+      :::{dropdown} Upgrades `repository-s3` plugin to AWS SDK v2
+      The `repository-s3` plugin now uses AWS SDK v2 instead of v1, as AWS will deprecate SDK v1 before the end of Elasticsearch 8.19’s support period. The two SDKs differ in behavior, which may require updates to your configuration.
+
+      **Impact:**
+      Existing `repository-s3` configurations may no longer be compatible. Notable differences in AWS SDK v2 include, but may not be limited to:
+      - AWS SDK v2 requires users to specify the region to use for signing requests, or else to run in an environment in which it can determine the correct region automatically. The older SDK used to determine the region based on the endpoint URL as specified with the `s3.client.${CLIENT_NAME}.endpoint` setting, together with other data drawn from the operating environment, and fell back to `us-east-1` if no better value was found.
+      - AWS SDK v2 does not support the EC2 IMDSv1 protocol.
+      - AWS SDK v2 does not support the `com.amazonaws.sdk.ec2MetadataServiceEndpointOverride` system property.
+      - AWS SDK v2 does not permit specifying a choice between HTTP and HTTPS so the `s3.client.${CLIENT_NAME}.protocol` setting is deprecated and no longer has any effect.
+      - AWS SDK v2 does not permit control over throttling for retries, so the `s3.client.${CLIENT_NAME}.use_throttle_retries` setting is deprecated and no longer has any effect.
+      - AWS SDK v2 requires the use of the V4 signature algorithm, therefore, the `s3.client.${CLIENT_NAME}.signer_override` setting is deprecated and no longer has any effect.
+      - AWS SDK v2 does not support the `log-delivery-write` canned ACL.
+      - AWS SDK v2 counts 4xx responses differently in its metrics reporting.
+      - AWS SDK v2 always uses the regional STS endpoint, whereas AWS SDK v2 could use either a regional endpoint or the global `https://sts.amazonaws.com` one.
+
+      **Action:**
+      Test the upgrade in a non-production environment. Adapt your configuration to the new SDK functionality. This includes, but may not be limited to, the following items:
+      - Specify the correct signing region using the `s3.client.${CLIENT_NAME}.region` setting on each node. {es} will try to determine the correct region based on the endpoint URL and other data drawn from the operating environment, but might not do so correctly in all cases.
+      - If you use IMDS to determine the availability zone of a node or to obtain credentials for accessing the EC2 API, ensure that it supports the IMDSv2 protocol.
+      - If applicable, discontinue use of the `com.amazonaws.sdk.ec2MetadataServiceEndpointOverride` system property.
+      - If applicable, specify that you wish to use the insecure HTTP protocol to access the S3 API by setting `s3.client.${CLIENT_NAME}.endpoint` to a URL which starts with `http://`.
+      - If applicable, discontinue use of the `log-delivery-write` canned ACL.
+
+      For more information, view [#126843](https://github.com/elastic/elasticsearch/pull/126843) (issue: [#120993](https://github.com/elastic/elasticsearch/issues/120993))
+      :::
     breaking:
       area: Cluster and node setting
       title: Upgrade `repository-s3` to AWS SDK v2
@@ -1279,6 +1325,20 @@ changelogs:
     type: breaking
     issues:
       - 122802
+    entryOverride: |
+      :::{dropdown} ES|QL now returns partial results by default
+      In previous versions, ES|QL queries failed entirely when any error occurred. As of 8.19.0, ES|QL returns partial results instead.
+
+      **Impact:**
+      Callers must check the `is_partial` flag in the response to determine whether the result is complete. Relying on full results without checking this flag may lead to incorrect assumptions about the response.
+
+      **Action:**
+      If partial results are not acceptable for your use case, you can disable this behavior by:
+      * Setting `allow_partial_results=false` in the query URL per request, or
+      * Setting the `esql.query.allow_partial_results` cluster setting to `false`.
+
+      For more information, view [#127351](https://github.com/elastic/elasticsearch/pull/127351) (issue: [#122802](https://github.com/elastic/elasticsearch/issues/122802))
+      :::
     breaking:
       area: ES|QL
       title: Allow partial results by default in ES|QL
@@ -1287,7 +1347,7 @@ changelogs:
       notable: true
       essSettingChange: false
   - pr: 127355
-    summary: '`text ==` and `text !=` pushdown'
+    summary: "`text ==` and `text !=` pushdown"
     area: ES|QL
     type: enhancement
     issues: []
@@ -1351,10 +1411,24 @@ changelogs:
     type: breaking
     issues:
       - 122651
+    entryOverride: |
+      :::{dropdown} Disallows mixing quoted and unquoted components in `FROM` index patterns
+      ES|QL no longer allows mixing quoted and unquoted parts in `FROM` index patterns (e.g. `FROM remote:"index"`). Previously, such patterns were parsed inconsistently and could result in misleading runtime errors.
+
+      **Impact:**
+      Queries using partially quoted index patterns—such as quoting only the index or only the remote cluster—will now be rejected at parse time. This change simplifies grammar handling and avoids confusing validation failures.
+
+      **Action:**
+      Ensure index patterns are either fully quoted or fully unquoted. For example:
+      * Valid: `FROM "remote:index"` or `FROM remote:index`
+      * Invalid: `FROM remote:"index"`, `FROM "remote":index`
+
+      For more information, view [#127636](https://github.com/elastic/elasticsearch/pull/127636) (issue: [#122651](https://github.com/elastic/elasticsearch/issues/122651))
+      :::
     breaking:
       area: ES|QL
       title: Disallow mixed quoted/unquoted patterns in FROM
-      details: "Previously, the ES|QL grammar allowed users to individually quote constituent strings in index patterns such as \"remote_cluster\":\"index_name\". This would allow users to write complex malformed index patterns that often slip through grammar and the subsequent validation. This could result in runtime errors that can be misleading. This change simplifies the grammar to early reject such malformed index patterns at the parsing stage, allowing users to write simpler queries and see more relevant and meaningful errors."
+      details: 'Previously, the ES|QL grammar allowed users to individually quote constituent strings in index patterns such as "remote_cluster":"index_name". This would allow users to write complex malformed index patterns that often slip through grammar and the subsequent validation. This could result in runtime errors that can be misleading. This change simplifies the grammar to early reject such malformed index patterns at the parsing stage, allowing users to write simpler queries and see more relevant and meaningful errors.'
       impact: Users can write queries with simpler index patterns and see more meaningful and relevant errors.
       notable: false
       essSettingChange: false
@@ -1462,6 +1536,18 @@ changelogs:
     area: ES|QL
     type: breaking
     issues: []
+    entryOverride: |
+      :::{dropdown} `skip_unavailable` now catches all remote cluster runtime errors in ES|QL
+      When `skip_unavailable` is set to `true`, ES|QL now treats all runtime errors from that cluster as non-fatal. Previously, this setting only applied to connectivity issues (i.e. when a cluster was unavailable).
+
+      **Impact:**
+      Errors such as missing indices on a remote cluster will no longer cause the query to fail. Instead, the cluster will appear in the response metadata as `skipped` or `partial`.
+
+      **Action:**
+      If your workflows rely on detecting remote cluster errors, review your use of `skip_unavailable` and adjust error handling as needed.
+
+      For more information, view [#128163](https://github.com/elastic/elasticsearch/pull/128163)
+      :::
     breaking:
       area: ES|QL
       title: Cluster setting "skip_unavailable" catches all runtime errors
@@ -1588,7 +1674,7 @@ changelogs:
     type: enhancement
     issues: []
   - pr: 128584
-    summary: '`InferenceService` support aliases'
+    summary: "`InferenceService` support aliases"
     area: Machine Learning
     type: enhancement
     issues: []
@@ -1815,7 +1901,7 @@ changelogs:
     type: enhancement
     issues: []
   - pr: 129413
-    summary: '`SageMaker` Elastic Payload'
+    summary: "`SageMaker` Elastic Payload"
     area: Machine Learning
     type: enhancement
     issues: []
@@ -1986,6 +2072,17 @@ changelogs:
     type: breaking
     issues:
       - 130378
+    entryOverride: |
+      :::{dropdown} Disallows parentheses in unquoted index patterns in ES|QL
+      To avoid ambiguity with subquery syntax, ES|QL no longer allows the use of `(` and `)` in unquoted index patterns.
+
+      **Impact:**
+      Queries that include parentheses in unquoted index names will now result in a parsing exception.
+
+      **Action:**
+      Update affected queries to quote index names that contain parentheses. For example, use `FROM "("foo")"` instead of `FROM (foo)`.
+      For more information, view [#130427](https://github.com/elastic/elasticsearch/pull/130427) (issue: [#130378](https://github.com/elastic/elasticsearch/issues/130378))
+      :::
     breaking:
       area: ES|QL
       title: Unquoted index patterns do not allow `(` and `)` characters

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

@@ -8,78 +8,166 @@ changelogs:
     type: bug
     issues:
       - 130071
+    entryOverride: |
+      :::{dropdown} Fix missing removal of query cancellation callback in QueryPhase
+      The timeout cancellation callback registered in `QueryPhase` via `addQueryCancellation` was not removed after the query phase completed.
+      This caused unintended timeouts or cancellations during subsequent phases under specific conditions (such as large datasets, low timeouts, and partial search results enabled).
+      [#130279](https://github.com/elastic/elasticsearch/pull/130279) resolves the issue and ensures predictable behavior by reintroducing the cleanup logic. (issue: [#130071](https://github.com/elastic/elasticsearch/issues/130071))
+      :::
   - pr: 131053
     summary: Split large pages on load sometimes
     area: ES|QL
     type: bug
     issues: []
+    entryOverride: |
+      :::{dropdown} Adds support for splitting large pages on load to avoid memory pressure
+      Loading large rows from a single segment occasionally created oversized pages when decoding values row-by-row, particularly for text and geo fields.
+      This could cause memory pressure or degraded performance.
+      [#131053](https://github.com/elastic/elasticsearch/pull/131053) resolves the issue by estimating the size of each page as rows are loaded.
+      If the estimated size exceeds a configurable `jumbo` threshold (defaulting to one megabyte), row loading stops early, the page is returned, and remaining rows are processed in subsequent iterations.
+      This prevents loading incomplete or oversized pages during data aggregation.
+      :::
   - pr: 131429
     summary: Prevent auto-sharding for data streams in LOOKUP index mode
     area: Data streams
     type: bug
     issues: []
+    entryOverride: |
+      :::{dropdown} Disables auto-sharding for LOOKUP index mode
+      Auto-sharding for data streams caused unsupported replica scaling when the index mode was set to `LOOKUP`.
+      This happened because lookup mappers do not support scaling beyond one replica.
+      [#131429](https://github.com/elastic/elasticsearch/pull/131429) resolves this issue by disabling auto-sharding for data streams with `LOOKUP` index mode, avoiding unsupported replica settings.
+      :::
   - pr: 131658
     summary: Fix `aggregate_metric_double` sorting and `mv_expand` issues
     area: ES|QL
     type: bug
     issues: []
+    entryOverride: |
+      :::{dropdown} Fixes `aggregate_metric_double` decoding and `mv_expand` behavior on multi-index queries
+      Sorting across multiple indices failed when one index contained an `aggregate_metric_double` field and another did not.
+      In this case, the missing field was encoded as `NullBlock` but later incorrectly decoded as `AggregateMetricDoubleBlock`, which expects four values. This mismatch caused decoding errors.
+      [#131658](https://github.com/elastic/elasticsearch/pull/131658) resolves the issue and also improves `mv_expand` by returning the input block unchanged for unsupported `AggregateMetricDoubleBlock` values, avoiding unnecessary errors.
+      :::
   - pr: 131680
     summary: Grant server module read/write entitlements for deprecated path setting "path.shared_data"
     area: Infra/Core
     type: bug
     issues: []
+    entryOverride: |
+      :::{dropdown} Grants server module read/write permissions for deprecated `path.shared_data` setting
+      Grants the server module read/write access to the deprecated `path.shared_data` setting.
+      [#131680](https://github.com/elastic/elasticsearch/pull/131680) resolves issues surfaced in internal testing and ensures compatibility with legacy configurations.
+      :::
   - pr: 131817
     summary: Change equals and hashcode for `ConstantNullBlock`
     area: ES|QL
     type: bug
     issues: []
+    entryOverride: |
+      :::{dropdown} Fixes inconsistent equality and hashcode behavior for `ConstantNullBlock`
+      Inconsistent equality checks caused `constantNullBlock.equals(anyDoubleBlock)` to return false, even when `doubleBlock.equals(constantNullBlock)` returned true.
+      This asymmetry led to unreliable comparisons and mismatched hashcodes when `ConstantNullBlock` was functionally equivalent to other standard blocks.
+      [#131817](https://github.com/elastic/elasticsearch/pull/131817) resolves the issue and ensures both equality and hashcode functions are symmetric for these block types.
+      :::
   - pr: 131917
     summary: Fix NPE on empty to_lower/to_upper call
     area: ES|QL
     type: bug
     issues:
       - 131913
+    entryOverride: |
+      :::{dropdown} Prevents null pointer exception for `to_lower` and `to_upper` with no parameters
+      Calling the `to_lower` or `to_upper` functions with no parameters caused a null pointer exception (NPE), instead of returning a clear error.
+      This behavior was a result of an older implementation of these functions.
+      [#131917](https://github.com/elastic/elasticsearch/pull/131917) resolves the issue and ensures that empty parameter calls now return the correct error message. (issue: [#131913](https://github.com/elastic/elasticsearch/issues/131913))
+      :::
   - pr: 131945
     summary: Restrict remote ENRICH after FORK
     area: ES|QL
     type: bug
     issues:
       - 131445
+    entryOverride: |
+      :::{dropdown} Disallows remote ENRICH after FORK in query plans
+      An invalid combination of `FORK` followed by a remote-only `ENRICH` caused incorrect query planning and failed executions. [#131945](https://github.com/elastic/elasticsearch/pull/131945) resolves the issue by explicitly disallowing this combination, preventing invalid plans from being executed. (issue: [#131445](https://github.com/elastic/elasticsearch/issues/131445))
+      :::
   - pr: 131990
     summary: Prevent the trained model deployment memory estimation from double-counting allocations
     area: Machine Learning
     type: bug
     issues: []
+    entryOverride: |
+      :::{dropdown} Prevents double-counting of allocations in trained model deployment memory estimation
+      A recent refactor introduced a bug that caused the trained model memory estimation to double-count the number of allocations, leading to inflated memory usage projections.
+      [#131990](https://github.com/elastic/elasticsearch/pull/131990) resolves the issue by reverting the change and restoring accurate memory estimation for trained model deployments.
+      :::
   - pr: 132018
     summary: Fix decoding of non-ascii field names in ignored source
     area: Mapping
     type: bug
     issues: []
+    entryOverride: |
+      :::{dropdown} Fixes decoding failure for non-ASCII field names in `_ignored_source`
+      A decoding error occurred when field names in `_ignored_source` contained non-ASCII characters.
+      This happened because `String.length()` was used to calculate the byte length of the field name, which only works correctly for ASCII characters.
+      [#132018](https://github.com/elastic/elasticsearch/pull/132018) resolves the issue by using the actual byte array length of the encoded field name, ensuring proper decoding regardless of character encoding.
+      :::
   - pr: 132088
     summary: Fix combine result for `ingest_took`
     area: ES|QL
     type: bug
     issues: []
+    entryOverride: |
+      :::{dropdown} Fixes incorrect `ingest_took` value when combining bulk responses
+      Combining two `BulkResponse` objects with `ingest_took` set to `NO_INGEST_TOOK` resulted in a combined `ingest_took` value of `-2`, which was invalid.
+      This occurred because the combination logic failed to preserve the sentinel `NO_INGEST_TOOK` constant.
+      [#132088](https://github.com/elastic/elasticsearch/pull/132088) resolves the issue and ensures the result is correctly set to `NO_INGEST_TOOK` when applicable.
+      :::
   - pr: 132101
     summary: Simulate ingest API uses existing index mapping when `mapping_addition` is given
     area: Ingest Node
     type: bug
     issues: []
+    entryOverride: |
+      :::{dropdown} Fixes incorrect mapping resolution in simulate ingest API when `mapping_addition` is provided
+      When using the simulate ingest API with a `mapping_addition`, the system incorrectly ignored the existing mapping of the target index and instead applied the mapping from a matching index template, if one existed.
+      This caused mismatches between the index and simulation behavior.
+      [#132101](https://github.com/elastic/elasticsearch/pull/132101) resolves the issue and ensures that the index’s actual mapping is used when available, preserving consistency between simulation and execution.
+      :::
   - pr: 132162
     summary: Fix default missing index sort value of `data_nanos` pre 7.14
     area: Search
     type: bug
     issues:
       - 132040
+    entryOverride: |
+      :::{dropdown} Fixes index sort compatibility for `date_nanos` fields in indices created before 7.14
+      Indices created prior to version 7.14 that used an index sort on a `date_nanos` field could not be opened in more recent versions due to a mismatch in the default `index.sort.missing` value.
+      A change in version 7.14 modified the default from `Long.MIN_VALUE` to `0L`, which caused newer versions to reject those older indices.
+      [#132162](https://github.com/elastic/elasticsearch/pull/132162) resolves the issue by restoring the expected default value for indices created before 7.14, allowing them to open successfully in newer versions. (issue: [#132040](https://github.com/elastic/elasticsearch/issues/132040))
+      :::
   - pr: 132167
     summary: Deal with internally created IN in a different way for EQL
     area: EQL
     type: bug
     issues:
       - 118621
+    entryOverride: |
+      :::{dropdown} Resolves EQL parsing failure for IP-mapped fields in `OR` expressions
+      Parsing EQL queries failed when comparing the same IP-mapped field to multiple values joined by an `OR` expression.
+      This occurred because lookup operators were internally rewritten into `IN` expressions, which are unsupported for IP-type fields.
+      [#132167](https://github.com/elastic/elasticsearch/pull/132167) resolves the issue and ensures EQL can now successfully parse and execute such or queries involving IP fields. (issue: [#118621](https://github.com/elastic/elasticsearch/issues/118621))
   - pr: 132260
     summary: FIx Driver creating status with a live list of operators
     area: ES|QL
     type: bug
     issues:
       - 131564
+    entryOverride: |
+      :::{dropdown} Fixes `ConcurrentModificationException` caused by live operator list
+      A `ConcurrentModificationException` caused test failures in `CrossClusterAsyncEnrichStopIT.testEnrichAfterStop` under certain conditions.
+      This happened because the ES|QL driver added a live operator list to the `DriverStatus` object, which could be modified while the status was being serialized.
+      [#132260](https://github.com/elastic/elasticsearch/pull/132260) fixes the issue by copying the operator list before storing it, preventing concurrent changes during status reads.
+      (issue: [#131564](https://github.com/elastic/elasticsearch/issues/131564))
+      :::

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

@@ -8,6 +8,12 @@ changelogs:
     type: bug
     issues:
       - 132272
+    entryOverride: |
+      :::{dropdown} Validates parent aggregation type in `bucket_script`
+      The `bucket_script` pipeline aggregation didn’t validate that its parent aggregation was a multi-bucket aggregation.
+      This caused a `ClassCastException` at runtime when the parent was not multi-bucket.
+      [#132320](https://github.com/elastic/elasticsearch/pull/132320) adds a validation step so the aggregation fails early, preventing the runtime error. (issue: [#132272](https://github.com/elastic/elasticsearch/issues/132272))
+      :::
   - pr: 132387
     summary: "[ExtraHop & QualysGAV] Add `manage`, `create_index`, `read`, `index`, `write`, `delete`, permission for third party agent indices `kibana_system`"
     area: Authorization
@@ -19,18 +25,40 @@ changelogs:
     area: ES|QL
     type: bug
     issues: []
+    entryOverride: |
+      :::{dropdown} Fixes for `COPY_SIGN` function in ESQL
+      The `COPY_SIGN` function has been updated to better support the literal `NULL` in parameters.
+      [#132459](https://github.com/elastic/elasticsearch/pull/132459)
+      :::
   - pr: 132570
     summary: Always stop the timer when profiling the fetch phase
     area: Search
     type: bug
     issues: []
+    entryOverride: |
+      :::{dropdown} Always stops the timer when profiling the fetch phase
+      Exceptions in fetch sub-phases (for example, `setNextReader`) left the profiling timer running, causing mismatched start/stop calls and errors.
+      [#132570](https://github.com/elastic/elasticsearch/pull/132570) ensures the `timer.stop()` call always stops.
+      :::
   - pr: 132593
     summary: Strings outside BMP have 2 chars per code points
     area: Mapping
     type: bug
     issues: []
+    entryOverride: |
+      :::{dropdown} Calculates text string length correctly for code points outside BMP
+      Strings parsed with the optimized UTF-8 parsing path had incorrect length calculations for characters outside the basic multilingual plane (BMP).
+      These characters require two UTF-16 code units, but the optimized path did not account for this, causing mismatches with the non-optimized path.
+      [#132593](https://github.com/elastic/elasticsearch/pull/132593) fixes the calculation to ensure consistent and correct string lengths.
+      :::
   - pr: 132597
     summary: Use local segment `fieldInfos` to lookup tsdb merge stats
     area: Codec
     type: bug
     issues: []
+    entryOverride: |
+      :::{dropdown} Uses local segment `fieldInfos` for TSDB merge stats
+      Merging shrink TSDB or LogsDB indices in versions 8.19 or 9.1+ could fail when using `addIndexes` to combine Lucene segments directly.
+      In these cases, the `fieldInfos` value could differ between shards and the merged segment, causing incorrect merge statistics.
+      PR [#132597](https://github.com/elastic/elasticsearch/pull/132597) updates the process to use `fieldInfos` from each segment instead of the merged segment, ensuring accurate stats and preventing merge failures.
+      :::