From 09df78b9671013ad9f510ca060b6b714da752bf4 Mon Sep 17 00:00:00 2001
From: Brian Seeders <brian.seeders@elastic.co>
Date: Wed, 2 Apr 2025 13:28:03 -0400
Subject: [PATCH] [9.0] Add a changelog entry for breaking change PR #90529

---
 docs/changelog/90529.yaml | 18 ++++++++++++++++++
 1 file changed, 18 insertions(+)
 create mode 100644 docs/changelog/90529.yaml

diff --git a/docs/changelog/90529.yaml b/docs/changelog/90529.yaml
new file mode 100644
index 0000000000000..75ce00a5b793f
--- /dev/null
+++ b/docs/changelog/90529.yaml
@@ -0,0 +1,18 @@
+pr: 90529
+summary: Update the response format when detailed error information is disabled
+area: Infra/Core
+type: breaking
+issues:
+  - 89387
+breaking:
+  title: Update the response format when detailed error information is disabled
+  area: REST API
+  details: |
+    Previously, if `http.detailed_errors.enabled` was set to `false`, error responses would
+    lack `type` and `reason` fields. Now, errors will always have these fields,
+    regardless of the `detailed_errors` setting.
+  impact: |
+    If using `http.detailed_errors.enabled: false`, ensure that anything
+    interacting with the REST API will be able to handle the added presence of
+    `type` and `reason` fields for errors.
+  notable: false