Skip to content

Pin 8.13 to transport ~8.4.1 #2217

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

Pin 8.13 to transport ~8.4.1 #2217

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
87 changes: 84 additions & 3 deletions docs/changelog.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,9 +8,11 @@
==== Fixes

[discrete]
===== Upgrade transport version to 8.4.1 https://github.com/elastic/elasticsearch-js/pull/2200[#2200]
===== Pin @elastic/transport to `~8.4.1`

v8.13.0 was released depending on v8.4.0 of `@elastic/transport` instead of v8.4.1, which fixes a bug related to data redaction on error objects.
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
Expand All @@ -32,6 +34,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

Expand All @@ -58,14 +71,27 @@ 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`

You can find all the API changes
https://www.elastic.co/guide/en/elasticsearch/reference/8.12/release-notes-8.12.0.html[here].

== Release notes

[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

Expand All @@ -85,6 +111,17 @@ https://www.elastic.co/guide/en/elasticsearch/reference/8.11/release-notes-8.11.

See <<redaction>> 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

Expand All @@ -97,6 +134,17 @@ See <<redaction>> 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

Expand Down Expand Up @@ -133,6 +181,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 @@ -178,6 +237,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 @@ -187,6 +257,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
2 changes: 1 addition & 1 deletion package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -83,7 +83,7 @@
"zx": "^7.2.2"
},
"dependencies": {
"@elastic/transport": "^8.4.1",
"@elastic/transport": "~8.4.1",
"tslib": "^2.4.0"
},
"tap": {
Expand Down