You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: docs/changelog.asciidoc
+68-2
Original file line number
Diff line number
Diff line change
@@ -1,11 +1,22 @@
1
1
[[changelog-client]]
2
2
== Release notes
3
3
4
+
[discrete]
5
+
=== 8.11.1
6
+
7
+
[discrete]
8
+
==== Fixes
9
+
10
+
[discrete]
11
+
===== Bump @elastic/transport to `~8.4.0`
12
+
13
+
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.
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.
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.
67
+
35
68
[discrete]
36
69
=== 8.9.1
37
70
@@ -68,6 +101,17 @@ In the https://www.elastic.co/guide/en/elasticsearch/client/javascript-api/curre
68
101
69
102
The `user-agent` header the client used to connect to Elasticsearch was using a non-standard format that has been improved.
70
103
104
+
[discrete]
105
+
=== 8.8.2
106
+
107
+
[discrete]
108
+
==== Fixes
109
+
110
+
[discrete]
111
+
===== Bump @elastic/transport to `~8.3.2`
112
+
113
+
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.
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.
115
159
160
+
[discrete]
161
+
=== 8.7.3
162
+
163
+
[discrete]
164
+
==== Fixes
165
+
166
+
[discrete]
167
+
===== Bump @elastic/transport to `~8.3.1`
168
+
169
+
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.
170
+
116
171
[discrete]
117
172
=== 8.7.0
118
173
@@ -122,6 +177,17 @@ Prior releases contained a bug where type declarations for legacy types that inc
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.
0 commit comments