Update release notes for BC6 (#87912)

Author: craigtaverner

docs/changelog/85958.yaml

@@ -7,12 +7,12 @@ issues: []
 highlight:
   title: Question answering NLP task
   body: |-
-    We introduce a new question answering NLP task in 8.3. This task extracts 
-    the relevant section that answers a specific question from a larger context. 
-    This is especially suited to search requests against large documents. You 
-    can find an example of extracting an answer from a larger wiki article about 
+    We introduce a new question answering NLP task in 8.3. This task extracts
+    the relevant section that answers a specific question from a larger context.
+    This is especially suited to search requests against large documents. You
+    can see an example of extracting an answer from a larger wiki article about
     Tower Bridge below.
-    
+
     [role="screenshot"]
     image::../images/nlp-qa-rh.png[A screenshot of a question answering NLP task in {kib}]
-  notable: true
+  notable: true

docs/changelog/86501.yaml

@@ -6,7 +6,7 @@ issues: []
 highlight:
   title: Transforms support range aggregation
   body: |-
-    Now it is possible to use the range aggregations in {transforms}. 
-    {transforms-cap} didn’t support multi-bucket aggregations, but this 
-    limitation no longer exist.
-  notable: true
+    Now it is possible to use the range aggregations in {transforms}.
+    {transforms-cap} didn’t support multi-bucket aggregations, but this
+    limitation no longer exists.
+  notable: true

docs/reference/release-notes/8.3.0.asciidoc

@@ -37,6 +37,7 @@ CCR::
 
 Cluster Coordination::
 * Add `master_timeout` support to voting config exclusions APIs {es-pull}86670[#86670]
+* Small fixes to clear voting config excls API {es-pull}87828[#87828]
 
 Discovery-Plugins::
 * [discovery-gce] Fix initialisation of transport in FIPS mode {es-pull}85817[#85817] (issue: {es-issue}85803[#85803])
@@ -66,6 +67,9 @@ ILM+SLM::
 Indices APIs::
 * Make `GetIndexAction` cancellable {es-pull}87681[#87681]
 
+Infra/Circuit Breakers::
+* Make CBE message creation more robust {es-pull}87881[#87881]
+
 Infra/Core::
 * Adjust osprobe assertion for burst cpu {es-pull}86990[#86990]
 * Clean up `DeflateCompressor` after exception {es-pull}87163[#87163] (issue: {es-issue}87160[#87160])
@@ -133,6 +137,7 @@ Search::
 * Fields API to allow fetching values when `_source` is disabled {es-pull}87267[#87267] (issue: {es-issue}87072[#87072])
 * Fix `_terms_enum` on unconfigured `constant_keyword` {es-pull}86191[#86191] (issues: {es-issue}86187[#86187], {es-issue}86267[#86267])
 * Fix status code when open point in time without `keep_alive` {es-pull}87011[#87011] (issue: {es-issue}87003[#87003])
+* Handle empty point values in `DiskUsage` API {es-pull}87826[#87826] (issue: {es-issue}87761[#87761])
 * Make sure to rewrite explain query on coordinator {es-pull}87013[#87013] (issue: {es-issue}64281[#64281])
 
 Security::
@@ -144,6 +149,7 @@ Snapshot/Restore::
 * Distinguish missing and invalid repositories {es-pull}85551[#85551] (issue: {es-issue}85550[#85550])
 * Fork after calling `getRepositoryData` from `StoreRecovery` {es-pull}87264[#87264] (issue: {es-issue}87237[#87237])
 * Fork after calling `getRepositoryData` from `StoreRecovery` {es-pull}87254[#87254] (issue: {es-issue}87237[#87237])
+* Throw exception on illegal `RepositoryData` updates {es-pull}87654[#87654]
 * Upgrade Azure SDK to 12.16.0 {es-pull}86135[#86135]
 
 TSDB::
@@ -288,6 +294,7 @@ TSDB::
 
 Transform::
 * Prefer secondary auth headers for transforms {es-pull}86757[#86757]
+* Support `range` aggregation in transform {es-pull}86501[#86501]
 
 [[feature-8.3.0]]
 [float]
@@ -345,4 +352,7 @@ SQL::
 Search::
 * Update to public lucene 9.2.0 release {es-pull}87162[#87162]
 
+Snapshot/Restore::
+* Upgrade GCS Plugin to 1.118.1 {es-pull}87800[#87800]
+
 

docs/reference/release-notes/highlights.asciidoc

@@ -59,6 +59,18 @@ a StackOverflowError. There are some side effects also:
 - There is a slight speed up for pipelines with multiple scripts, and a slight
 slowdown for pipelines without scripts.
 
+[discrete]
+[[question_answering_nlp_task]]
+=== {es-pull}85958[Question answering NLP task]
+We introduce a new question answering NLP task in 8.3. This task extracts
+the relevant section that answers a specific question from a larger context.
+This is especially suited to search requests against large documents. You
+can see an example of extracting an answer from a larger wiki article about
+Tower Bridge below.
+
+[role="screenshot"]
+image::../images/nlp-qa-rh.png[A screenshot of a question answering NLP task in {kib}]
+
 [discrete]
 [[add_support_for_dots_in_field_names_for_metrics_usecases]]
 === {es-pull}86166[Add support for dots in field names for metrics usecases]
@@ -111,6 +123,13 @@ for compliance or regulatory reasons, the occasional lookback or investigation,
 or to rehydrate parts of it. Access to the data is expected to be infrequent,
 and can therefore happen with limited performance and query capabilities.
 
+[discrete]
+[[transforms_support_range_aggregation]]
+=== {es-pull}86501[Transforms support range aggregation]
+Now it is possible to use the range aggregations in {transforms}.
+{transforms-cap} didn’t support multi-bucket aggregations, but this
+limitation no longer exists.
+
 [discrete]
 [[new_geo_grid_query]]
 === {es-pull}86596[New geo_grid query]