Skip to content

Commit 3cddb9b

Browse files
8.18.1 release notes (#6802) (#6829)
* First draft * Revisions * Update docs/release-notes/8.18.asciidoc Co-authored-by: Gabriel Landau <[email protected]> * Update docs/release-notes/8.18.asciidoc Co-authored-by: Gabriel Landau <[email protected]> * Update docs/release-notes/8.18.asciidoc Co-authored-by: Gabriel Landau <[email protected]> * Adds 216667 * space * Update ki description for endpoint bug * Adds ki about eql rules * remove char * Adds one more version --------- Co-authored-by: Gabriel Landau <[email protected]> (cherry picked from commit 67a4f7e) Co-authored-by: Nastasha Solomon <[email protected]>
1 parent 089438e commit 3cddb9b

File tree

2 files changed

+38
-1
lines changed

2 files changed

+38
-1
lines changed

docs/release-notes.asciidoc

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -3,6 +3,7 @@
33

44
This section summarizes the changes in each release.
55

6+
* <<release-notes-8.18.1, {elastic-sec} version 8.18.1>>
67
* <<release-notes-8.18.0, {elastic-sec} version 8.18.0>>
78
* <<release-notes-8.17.5, {elastic-sec} version 8.17.5>>
89
* <<release-notes-8.17.4, {elastic-sec} version 8.17.4>>

docs/release-notes/8.18.asciidoc

Lines changed: 37 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,38 @@
11
[[release-notes-header-8.18.0]]
22
== 8.18
33

4+
[discrete]
5+
[[release-notes-8.18.1]]
6+
=== 8.18.1
7+
8+
// tag::known-issue[]
9+
[discrete]
10+
.The technical preview badge incorrectly displays on the alert suppression fields for event correlation rules
11+
[%collapsible]
12+
====
13+
*Details* +
14+
On April 8, 2025, it was discovered that alert suppression for event correlation rules is incorrectly shown as being in technical preview when you create a new rule. For more information, check https://github.com/elastic/docs-content/issues/1021[#1021].
15+
16+
====
17+
// end::known-issue[]
18+
19+
[discrete]
20+
[[enhancements-8.18.1]]
21+
==== Enhancements
22+
* Updates the **MITRE ATT&CK® coverage** page mapping to `v16.1` ({kibana-pull}215026[#215026]).
23+
* Adds a background task to upgrade Agentless deployments after {kib} has been upgraded ({kibana-pull}207143[#207143]).
24+
* Improves {elastic-defend}'s' CPU usage on systems with very high event volumes.
25+
26+
[discrete]
27+
[[bug-fixes-8.18.1]]
28+
==== Fixes
29+
* Removes the check for unused connector roles ({kibana-pull}219358[#219358]).
30+
* Simplifies and improves the rule import error message ({kibana-pull}218701[#218701]).
31+
* Fixes the related integrations render performance on rule editing pages ({kibana-pull}217254[#217254]).
32+
* Prevents {esql} rules from timing out if the rule query takes longer than five minutes to complete ({kibana-pull}216667[#216667]).
33+
* Improves {elastic-defend}'s call site analysis logic.
34+
* Fixes a bug in {elastic-defend}'s redaction of diagnostics bundles.
35+
436
[discrete]
537
[[release-notes-8.18.0]]
638
=== 8.18.0
@@ -29,7 +61,7 @@ Duplicate your rules and enable them.
2961
[%collapsible]
3062
====
3163
*Details* +
32-
On April 8, 2025, it was discovered that alert suppression for event correlation rules is incorrectly shown as being in technical preview when you create a new rule. For more information, check (https://github.com/elastic/docs-content/issues/1021)[#1021].
64+
On April 8, 2025, it was discovered that alert suppression for event correlation rules is incorrectly shown as being in technical preview when you create a new rule. For more information, check https://github.com/elastic/docs-content/issues/1021[#1021].
3365
3466
====
3567
// end::known-issue[]
@@ -44,6 +76,10 @@ When you install an {elastic-defend} integration or a new agent policy for this
4476
4577
*Workaround* +
4678
To resolve this issue, before you add an {elastic-defend} integration to a policy in {fleet}, apply any pending prebuilt rule updates. This will prevent rule actions, exceptions, and customizations from being overwritten.
79+
80+
*Resolved* +
81+
This issue is fixed in {stack} versions 8.17.6, 8.18.1, and 9.0.1.
82+
4783
====
4884
// end::known-issue[]
4985

0 commit comments

Comments
 (0)