Skip to content

Switch 8.9 clients to only get patch updates to transport #2213

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Apr 9, 2024
Merged

Switch 8.9 clients to only get patch updates to transport #2213

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
44 changes: 44 additions & 0 deletions docs/changelog.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,17 @@
[[changelog-client]]
== Release notes

[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

Expand Down Expand Up @@ -37,6 +48,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

Expand Down Expand Up @@ -82,6 +104,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

Expand All @@ -91,6 +124,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

Expand Down
6 changes: 3 additions & 3 deletions package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
{
"name": "@elastic/elasticsearch",
"version": "8.9.1",
"versionCanary": "8.9.1-canary.1",
"version": "8.9.2",
"versionCanary": "8.9.2-canary.0",
"description": "The official Elasticsearch client for Node.js",
"main": "index.js",
"types": "index.d.ts",
Expand Down Expand Up @@ -86,7 +86,7 @@
"zx": "^7.2.2"
},
"dependencies": {
"@elastic/transport": "^8.3.4",
"@elastic/transport": "~8.3.4",
"tslib": "^2.4.0"
},
"tap": {
Expand Down
Loading