[Backport 8.11] 8.11.0 changelog (#2101)

* Changelog for 8.11.0

* Add redaction docs link to changelog

docs/advanced-config.asciidoc

@@ -92,6 +92,7 @@ const client = new Client({
 ----
 
 [discrete]
+[[redaction]]
 ==== Redaction of potentially sensitive data
 
 When the client raises an `Error` that originated at the HTTP layer, like a `ConnectionError` or `TimeoutError`, a `meta` object is often attached to the error object that includes metadata useful for debugging, like request and response information. Because this can include potentially sensitive data, like authentication secrets in an `Authorization` header, the client takes measures to redact common sources of sensitive data when this metadata is attached and serialized.

docs/changelog.asciidoc

@@ -1,6 +1,25 @@
 [[changelog-client]]
 == Release notes
 
+[discrete]
+=== 8.11.0
+
+[discrete]
+=== Features
+
+[discrete]
+===== Support for Elasticsearch `v8.11.0`
+
+You can find all the API changes
+https://www.elastic.co/guide/en/elasticsearch/reference/8.11/release-notes-8.11.0.html[here].
+
+[discrete]
+===== Enhanced support for redacting potentially sensitive data https://github.com/elastic/elasticsearch-js/pull/2095[#2095]
+
+`@elastic/transport` https://github.com/elastic/elastic-transport-js/releases/tag/v8.4.0[version 8.4.0] introduces enhanced measures for ensuring that request metadata attached to some `Error` objects is redacted. This functionality is primarily to address custom logging solutions that don't use common serialization methods like `JSON.stringify`, `console.log`, or `util.inspect`, which were already accounted for.
+
+See <<redaction>> for more information.
+
 [discrete]
 === 8.10.0
 

package.json

@@ -1,7 +1,7 @@
 {
   "name": "@elastic/elasticsearch",
   "version": "8.11.0",
-  "versionCanary": "8.11.0-canary.1",
+  "versionCanary": "8.11.0-canary.0",
   "description": "The official Elasticsearch client for Node.js",
   "main": "index.js",
   "types": "index.d.ts",