8.16.1 Release notes (#6178)

* First draft

* First draft

* Second draft

* Fixes issue

* Update docs/release-notes/8.16.asciidoc

Co-authored-by: Benjamin Ironside Goldstein <[email protected]>

* Update docs/release-notes/8.16.asciidoc

Co-authored-by: Benjamin Ironside Goldstein <[email protected]>

---------

Co-authored-by: Benjamin Ironside Goldstein <[email protected]>
(cherry picked from commit 4450b05)

Author: 2 people

docs/release-notes.asciidoc

@@ -3,6 +3,7 @@
 
 This section summarizes the changes in each release.
 
+* <<release-notes-8.16.1, {elastic-sec} version 8.16.1>>
 * <<release-notes-8.16.0, {elastic-sec} version 8.16.0>>
 * <<release-notes-8.15.4, {elastic-sec} version 8.15.4>>
 * <<release-notes-8.15.3, {elastic-sec} version 8.15.3>>

docs/release-notes/8.16.asciidoc

@@ -1,6 +1,22 @@
 [[release-notes-header-8.16.0]]
 == 8.16
 
+[discrete]
+[[release-notes-8.16.1]]
+=== 8.16.1
+
+[discrete]
+[[bug-fixes-8.16.1]]
+==== Bug fixes
+* Fixes a bug that caused the **Alerts** page to crash if you upgraded to 8.16 and accessed the page in a non-default {kib} space ({kibana-pull}200058[#200058]).
+* Fixes a bug that caused the Elastic AI Assistant Knowledge Base to fail if the current user had a colon (`:`) in their username and attempted to access Knowledge Base entries ({kibana-pull}200131[#200131]).
+* Fixes a bug that made values unavailable for the Knowledge Base **Index** field, which lets you specify an index as a knowledge source ({kibana-pull}199990[#199990]).
+* Fixes a bug that unset the `required_fields` field if you updated a rule by sending a `PATCH` request that didn't contain the `required_fields` field ({kibana-pull}199901[#199901]).
+* Fixes an issue that prevented you from successfully importing TSV files with asset criticality data if you were on Windows ({kibana-pull}199791[#199791]).
+* Fixes the entity store initialization error that was caused by risk engine failures. Now, when you upgrade to 8.16.1, or follow the standard flow for initializing the entity store, the risk engine no longer fails while deleting the component template. In addition, the index template will correctly reference the new component template, ensuring the successful initialization of the entity store ({kibana-pull}199734[#199734]).
+* Improves the warning message that displays when asset criticality assignments are duplicated during the bulk assignment flow ({kibana-pull}199651[#199651]).
+* Fixes a time skew bug that occurred when Linux virtual machines using eBPF event probes were suspended and then resumed.
+
 [discrete]
 [[release-notes-8.16.0]]
 === 8.16.0
@@ -18,7 +34,11 @@
 Updating a Knowledge Base entry of type "index" results in an error.
 
 *Workaround* +
-Instead of updating an "index" entry, delete it and add it again with the desired changes.
+
+Upgrade to 8.16.1. Alternatively, instead of updating an "index" entry, delete it and add it again with the desired changes.
+
+*Resolved* +
+On November 21, 2024, this issue was resolved.
 
 ====
 // end::known-issue[]
@@ -65,7 +85,10 @@ On November 12, 2024, it was discovered that manually running a custom query rul
 On November 14, 2024, it was discovered that the **Alerts** page would crash and display an `Unable to load` error if you upgraded to 8.16 and accessed the page in a non-default {kib} space.
 
 *Workaround* +
-Manually edit your browser's local storage and refresh the **Alerts** page:
+
+Upgrade to 8.16.1. 
+
+Alternatively, manually edit your browser's local storage and refresh the **Alerts** page:
 
 NOTE: These instructions only apply to the Google Chrome browser. Modify the steps based on the browser you're using.
 
@@ -75,15 +98,12 @@ NOTE: These instructions only apply to the Google Chrome browser. Modify the ste
 . Search for the `siem.<space_name>.pageFilters` key, right-click on the value, then click *Delete*. If you have multiple non-default spaces, do this for each space.
 . Refresh the **Alerts** page to reload it.
 
+*Resolved* +
+On November 21, 2024, this issue was resolved.
+
 ====
 // end::known-issue-53[]
 
-[discrete]
-[[breaking-changes-8.16.0]]
-==== Breaking changes
-
-* During shutdown, {kib} now waits for all the ongoing requests to complete according to the `server.shutdownTimeout` setting. During that period, the incoming socket is closed and any new incoming requests are rejected. Before this update, new incoming requests received a response with the status code 503 and body `{ "message": "{kib} is shutting down and not accepting new incoming requests" }`.
-
 [discrete]
 [[features-8.16.0]]
 ==== New features