From 9eaf6bf21813123fcbcf76cf131ae38fb8fd3dd8 Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" <41898282+github-actions[bot]@users.noreply.github.com> Date: Tue, 9 Apr 2024 15:15:47 -0500 Subject: [PATCH] [Backport 8.14] Backport changelogs from other minor releases (#2219) (cherry picked from commit b857d8ee71fa28ce6378746edfd445a60fbd283a) Co-authored-by: Josh Mock --- docs/changelog.asciidoc | 95 ++++++++++++++++++++++++++++++++++++++++- 1 file changed, 94 insertions(+), 1 deletion(-) diff --git a/docs/changelog.asciidoc b/docs/changelog.asciidoc index dc918e32f..cb0ddb673 100644 --- a/docs/changelog.asciidoc +++ b/docs/changelog.asciidoc @@ -4,11 +4,27 @@ [discrete] === 8.14.0 +[discrete] +==== Features + [discrete] ===== `onSuccess` callback added to bulk helper The bulk helper now supports an `onSuccess` callback that will be called for each successful operation. https://github.com/elastic/elasticsearch-js/pull/2199[#2199] +[discrete] +=== 8.13.1 + +[discrete] +==== Fixes + +[discrete] +===== Pin @elastic/transport to `~8.4.1` + +Switching from `^8.4.1` to `~8.4.1` ensures 8.13 client users are not required to update to Node.js v18+, which is a new requirement set by `@elastic/transport` v8.5.0. See https://github.com/elastic/elastic-transport-js/issues/91[elastic/elastic-transport-js#91] for details. + +v8.13.0 was also released depending on v8.4.0 of `@elastic/transport` instead of v8.4.1, which was unintentional. + [discrete] === 8.13.0 @@ -29,6 +45,17 @@ https://www.elastic.co/guide/en/elasticsearch/reference/8.13/release-notes-8.13. When instantiating a client, any connection-related defaults (e.g. `requestTimeout`) set on that client instance would not be inherited by nodes if they were entered as strings rather than a `ConnectionOptions` object. +[discrete] +=== 8.12.3 + +[discrete] +==== Fixes + +[discrete] +===== Bump @elastic/transport to `~8.4.1` + +Switching from `^8.4.1` to `~8.4.1` ensures 8.12 client users are not required to update to Node.js v18+, which is a new requirement set by `@elastic/transport` v8.5.0. See https://github.com/elastic/elastic-transport-js/issues/91[elastic/elastic-transport-js#91] for details. + [discrete] === 8.12.2 @@ -55,7 +82,7 @@ The failing state could be reached when a server's response times are slower tha === 8.12.0 [discrete] -==== Features +=== Features [discrete] ===== Support for Elasticsearch `v8.12.0` @@ -63,6 +90,17 @@ The failing state could be reached when a server's response times are slower tha You can find all the API changes https://www.elastic.co/guide/en/elasticsearch/reference/8.12/release-notes-8.12.0.html[here]. +[discrete] +=== 8.11.1 + +[discrete] +==== Fixes + +[discrete] +===== Bump @elastic/transport to `~8.4.0` + +Switching from `^8.4.0` to `~8.4.0` ensures 8.11 client users are not required to update to Node.js v18+, which is a new requirement set by `@elastic/transport` v8.5.0. See https://github.com/elastic/elastic-transport-js/issues/91[elastic/elastic-transport-js#91] for details. + [discrete] === 8.11.0 @@ -82,6 +120,17 @@ https://www.elastic.co/guide/en/elasticsearch/reference/8.11/release-notes-8.11. See <> for more information. +[discrete] +=== 8.10.1 + +[discrete] +==== Fixes + +[discrete] +===== Bump @elastic/transport to `~8.3.4` + +Switching from `^8.3.4` to `~8.3.4` ensures 8.10 client users are not required to update to Node.js v18+, which is a new requirement set by `@elastic/transport` v8.5.0. See https://github.com/elastic/elastic-transport-js/issues/91[elastic/elastic-transport-js#91] for details. + [discrete] === 8.10.0 @@ -94,6 +143,17 @@ See <> for more information. You can find all the API changes https://www.elastic.co/guide/en/elasticsearch/reference/8.10/release-notes-8.10.0.html[here]. +[discrete] +=== 8.9.2 + +[discrete] +==== Fixes + +[discrete] +===== Bump @elastic/transport to `~8.3.4` + +Switching from `^8.3.4` to `~8.3.4` ensures 8.9 client users are not required to update to Node.js v18+, which is a new requirement set by `@elastic/transport` v8.5.0. See https://github.com/elastic/elastic-transport-js/issues/91[elastic/elastic-transport-js#91] for details. + [discrete] === 8.9.1 @@ -130,6 +190,17 @@ In the https://www.elastic.co/guide/en/elasticsearch/client/javascript-api/curre The `user-agent` header the client used to connect to Elasticsearch was using a non-standard format that has been improved. +[discrete] +=== 8.8.2 + +[discrete] +==== Fixes + +[discrete] +===== Bump @elastic/transport to `~8.3.2` + +Switching from `^8.3.2` to `~8.3.2` ensures 8.8 client users are not required to update to Node.js v18+, which is a new requirement set by `@elastic/transport` v8.5.0. See https://github.com/elastic/elastic-transport-js/issues/91[elastic/elastic-transport-js#91] for details. + [discrete] === 8.8.1 @@ -175,6 +246,17 @@ https://www.elastic.co/guide/en/elasticsearch/reference/8.8/release-notes-8.8.0. Prior releases contained a bug where type declarations for legacy types that include a `body` key were not actually importing the type that includes the `body` key. +[discrete] +=== 8.7.3 + +[discrete] +==== Fixes + +[discrete] +===== Bump @elastic/transport to `~8.3.1` + +Switching from `^8.3.1` to `~8.3.1` ensures 8.7 client users are not required to update to Node.js v18+, which is a new requirement set by `@elastic/transport` v8.5.0. See https://github.com/elastic/elastic-transport-js/issues/91[elastic/elastic-transport-js#91] for details. + [discrete] === 8.7.0 @@ -184,6 +266,17 @@ Prior releases contained a bug where type declarations for legacy types that inc You can find all the API changes https://www.elastic.co/guide/en/elasticsearch/reference/8.7/release-notes-8.7.0.html[here]. +[discrete] +=== 8.6.1 + +[discrete] +==== Fixes + +[discrete] +===== Bump @elastic/transport to `~8.3.1` + +Switching from `^8.3.1` to `~8.3.1` ensures 8.6 client users are not required to update to Node.js v18+, which is a new requirement set by `@elastic/transport` v8.5.0. See https://github.com/elastic/elastic-transport-js/issues/91[elastic/elastic-transport-js#91] for details. + [discrete] === 8.6.0