Skip to content

Add recent releases to changelog #2633

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.

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
Feb 24, 2025
Merged
Changes from all commits
Commits
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
32 changes: 32 additions & 0 deletions docs/changelog.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -17,6 +17,22 @@ In 8.0, the top-level `body` parameter that was available on all API functions <

Setting HTTP timeouts on Elasticsearch requests goes against Elastic's recommendations. See <<timeout-best-practices>> for more information.

[discrete]
=== 8.17.1

[discrete]
==== Fixes

[discrete]
===== Improved support for Elasticsearch `v8.17`

Updated TypeScript types based on fixes and improvements to the Elasticsearch specification.

[discrete]
===== Report correct transport connection type in telemetry

The client's telemetry reporting mechanism was incorrectly reporting all traffic as using `HttpConnection` when the default is `UndiciConnection`. https://github.com/elastic/elasticsearch-js/issues/2324[#2324]

[discrete]
=== 8.17.0

Expand All @@ -29,6 +45,22 @@ Setting HTTP timeouts on Elasticsearch requests goes against Elastic's recommend
You can find all the API changes
https://www.elastic.co/guide/en/elasticsearch/reference/8.17/release-notes-8.17.0.html[here].

[discrete]
=== 8.16.4

[discrete]
==== Fixes

[discrete]
===== Improved support for Elasticsearch `v8.16`

Updated TypeScript types based on fixes and improvements to the Elasticsearch specification.

[discrete]
===== Report correct transport connection type in telemetry

The client's telemetry reporting mechanism was incorrectly reporting all traffic as using `HttpConnection` when the default is `UndiciConnection`. https://github.com/elastic/elasticsearch-js/issues/2324[#2324]

[discrete]
=== 8.16.3

Expand Down
Loading