From fb363fe5c3854bc8ec5a2baf06af93c8ef34d3a0 Mon Sep 17 00:00:00 2001
From: Tomas Della Vedova <delvedor@users.noreply.github.com>
Date: Thu, 23 Sep 2021 14:49:18 +0200
Subject: [PATCH] Changelog for 7.15 (#1557)

---
 docs/changelog.asciidoc | 54 +++++++++++++++++++++++++++++++++++++++++
 1 file changed, 54 insertions(+)

diff --git a/docs/changelog.asciidoc b/docs/changelog.asciidoc
index 6fd038426..e49a925a4 100644
--- a/docs/changelog.asciidoc
+++ b/docs/changelog.asciidoc
@@ -1,6 +1,60 @@
 [[changelog-client]]
 == Release notes
 
+[discrete]
+=== 7.15.0
+
+[discrete]
+==== Features
+
+[discrete]
+===== Support for Elasticsearch `v7.15`
+
+You can find all the API changes
+https://www.elastic.co/guide/en/elasticsearch/reference/7.14/release-notes-7.15.0.html[here].
+
+[discrete]
+===== Support mapbox content type https://github.com/elastic/elasticsearch-js/pull/1500[#1500]
+
+If you call an API that returns a mapbox conten type, the response body will be a buffer.
+
+[discrete]
+===== Support CA fingerprint validation https://github.com/elastic/elasticsearch-js/pull/1499[#1499]
+
+You can configure the client to only trust certificates that are signed by a specific CA certificate ( CA certificate pinning ) by providing a `caFingerprint` option. This will verify that the fingerprint of the CA certificate that has signed the certificate of the server matches the supplied value.
+a `caFingerprint` option, which will verify the supplied certificate authority fingerprint.
+You must configure a SHA256 digest.
+
+[source,js]
+----
+const { Client } = require('@elastic/elasticsearch')
+const client = new Client({
+  node: 'https://example.com'
+  auth: { ... },
+  // the fingerprint (SHA256) of the CA certificate that is used to sign the certificate that the Elasticsearch node presents for TLS.
+  caFingerprint: '20:0D:CA:FA:76:...',
+  ssl: {
+    // might be required if it's a self-signed certificate
+    rejectUnauthorized: false
+  }
+})
+----
+
+[discrete]
+===== Show the body as string if the response error can't be read as ES error  https://github.com/elastic/elasticsearch-js/pull/1509[#1509]
+
+Useful if the errored response does not come from Elasticsearch, but a proxy in the middle for example.
+
+[discrete]
+===== Always display request params and options in request event https://github.com/elastic/elasticsearch-js/pull/1531[#1531]
+
+In some edge cases the params and options weren't available in observabilty events, now they are always defined.
+
+[discrete]
+===== Always emit request aborted event https://github.com/elastic/elasticsearch-js/pull/1534[#1534]
+
+If the client is busy running an async operation, the `.abort()` call might be executed before sending the actual request. In such case, the error was swallowed, now it will always be emitted, either in the `request` or `response` event.
+
 [discrete]
 === 7.14.0