Skip to content

Commit 50ee3fc

Browse files
JoshMockJoshMock
authored
Switch 8.12 clients to only get patch updates to transport (#2216)
1 parent 745a838 commit 50ee3fc

File tree

2 files changed

+84
-5
lines changed

2 files changed

+84
-5
lines changed

‎docs/changelog.asciidoc

+81-2
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,17 @@
11
[[changelog-client]]
22
== Release notes
33

4+
[discrete]
5+
=== 8.12.3
6+
7+
[discrete]
8+
==== Fixes
9+
10+
[discrete]
11+
===== Bump @elastic/transport to `~8.4.1`
12+
13+
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.
14+
415
[discrete]
516
=== 8.12.2
617

@@ -35,11 +46,24 @@ The failing state could be reached when a server's response times are slower tha
3546
You can find all the API changes
3647
https://www.elastic.co/guide/en/elasticsearch/reference/8.12/release-notes-8.12.0.html[here].
3748

49+
== Release notes
50+
51+
[discrete]
52+
=== 8.11.1
53+
54+
[discrete]
55+
==== Fixes
56+
57+
[discrete]
58+
===== Bump @elastic/transport to `~8.4.0`
59+
60+
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.
61+
3862
[discrete]
3963
=== 8.11.0
4064

4165
[discrete]
42-
=== Features
66+
==== Features
4367

4468
[discrete]
4569
===== Support for Elasticsearch `v8.11.0`
@@ -54,18 +78,40 @@ https://www.elastic.co/guide/en/elasticsearch/reference/8.11/release-notes-8.11.
5478

5579
See <<redaction>> for more information.
5680

81+
[discrete]
82+
=== 8.10.1
83+
84+
[discrete]
85+
==== Fixes
86+
87+
[discrete]
88+
===== Bump @elastic/transport to `~8.3.4`
89+
90+
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.
91+
5792
[discrete]
5893
=== 8.10.0
5994

6095
[discrete]
61-
=== Features
96+
==== Features
6297

6398
[discrete]
6499
===== Support for Elasticsearch `v8.10.0`
65100

66101
You can find all the API changes
67102
https://www.elastic.co/guide/en/elasticsearch/reference/8.10/release-notes-8.10.0.html[here].
68103

104+
[discrete]
105+
=== 8.9.2
106+
107+
[discrete]
108+
==== Fixes
109+
110+
[discrete]
111+
===== Bump @elastic/transport to `~8.3.4`
112+
113+
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.
114+
69115
[discrete]
70116
=== 8.9.1
71117

@@ -102,6 +148,17 @@ In the https://www.elastic.co/guide/en/elasticsearch/client/javascript-api/curre
102148

103149
The `user-agent` header the client used to connect to Elasticsearch was using a non-standard format that has been improved.
104150

151+
[discrete]
152+
=== 8.8.2
153+
154+
[discrete]
155+
==== Fixes
156+
157+
[discrete]
158+
===== Bump @elastic/transport to `~8.3.2`
159+
160+
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.
161+
105162
[discrete]
106163
=== 8.8.1
107164

@@ -147,6 +204,17 @@ https://www.elastic.co/guide/en/elasticsearch/reference/8.8/release-notes-8.8.0.
147204

148205
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.
149206

207+
[discrete]
208+
=== 8.7.3
209+
210+
[discrete]
211+
==== Fixes
212+
213+
[discrete]
214+
===== Bump @elastic/transport to `~8.3.1`
215+
216+
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.
217+
150218
[discrete]
151219
=== 8.7.0
152220

@@ -156,6 +224,17 @@ Prior releases contained a bug where type declarations for legacy types that inc
156224
You can find all the API changes
157225
https://www.elastic.co/guide/en/elasticsearch/reference/8.7/release-notes-8.7.0.html[here].
158226

227+
[discrete]
228+
=== 8.6.1
229+
230+
[discrete]
231+
==== Fixes
232+
233+
[discrete]
234+
===== Bump @elastic/transport to `~8.3.1`
235+
236+
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.
237+
159238
[discrete]
160239
=== 8.6.0
161240

‎package.json

+3-3
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
{
22
"name": "@elastic/elasticsearch",
3-
"version": "8.12.2",
4-
"versionCanary": "8.12.2-canary.1",
3+
"version": "8.12.3",
4+
"versionCanary": "8.12.3-canary.0",
55
"description": "The official Elasticsearch client for Node.js",
66
"main": "index.js",
77
"types": "index.d.ts",
@@ -83,7 +83,7 @@
8383
"zx": "^7.2.2"
8484
},
8585
"dependencies": {
86-
"@elastic/transport": "^8.4.1",
86+
"@elastic/transport": "~8.4.1",
8787
"tslib": "^2.4.0"
8888
},
8989
"tap": {

0 commit comments

Comments
 (0)