Add known issues entry about date rounding bug (#90721)

add entry to all affected versions

relates #90187

docs/reference/release-notes/8.4.1.asciidoc

@@ -11,3 +11,10 @@ Machine Learning::
 * [ML] Validate trained model deployment `queue_capacity` limit {es-pull}89611[#89611] (issue: {es-issue}89555[#89555])
 
 
+[[known-issues-8.4.1]]
+[float]
+=== Known issues
+
+* When using date range search with format that does not have all date fields (missing month or day)
+an incorrectly parsed date could be used. The workaround is to use date pattern with all date fields (year, month, day)
+(issue: {es-issue}90187[#90187])

docs/reference/release-notes/8.4.2.asciidoc

@@ -16,6 +16,11 @@ with the message "totalTermFreq must be at least docFreq". If you use the
 `cross_fields` scoring type, it is recommended that you skip version 8.4.2.
 This regression was fixed in version 8.4.3.
 
+* When using date range search with format that does not have all date fields (missing month or day)
+an incorrectly parsed date could be used. The workaround is to use date pattern with all date fields (year, month, day)
+(issue: {es-issue}90187[#90187])
+
+
 [[bug-8.4.2]]
 [float]
 === Bug fixes
@@ -78,5 +83,3 @@ Health::
 
 Packaging::
 * Update OpenJDK to 18.0.2.1 {es-pull}89535[#89535] (issue: {es-issue}89531[#89531])
-
-

docs/reference/release-notes/8.4.3.asciidoc

@@ -21,3 +21,10 @@ Ranking::
 * Ensure `cross_fields` always uses valid term statistics {es-pull}90314[#90314]
 
 
+[[known-issues-8.4.3]]
+[float]
+=== Known issues
+
+* When using date range search with format that does not have all date fields (missing month or day)
+an incorrectly parsed date could be used. The workaround is to use date pattern with all date fields (year, month, day)
+(issue: {es-issue}90187[#90187])

docs/reference/release-notes/8.5.0.asciidoc

@@ -277,3 +277,10 @@ Client::
 * Upgrade Apache Commons Logging to 1.2 {es-pull}85745[#85745] (issue: {es-issue}40305[#40305])
 
 
+[[known-issues-8.5.0]]
+[float]
+=== Known issues
+
+* When using date range search with format that does not have all date fields (missing month or day)
+an incorrectly parsed date could be used. The workaround is to use date pattern with all date fields (year, month, day)
+(issue: {es-issue}90187[#90187])