Skip to content

[Backport 9.1] Add changelog for 9.0.4 and 9.1.1 #2966

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
Aug 8, 2025
Merged

[Backport 9.1] Add changelog for 9.0.4 and 9.1.1 #2966

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
12 changes: 12 additions & 0 deletions docs/release-notes/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,6 +20,12 @@ To check for security updates, go to [Security announcements for the Elastic sta
% ### Fixes [elasticsearch-javascript-client-next-fixes]
% \*

## 9.1.1

### Fixes [elasticsearch-javascript-client-9.1.1-fixes]

- **Propagate telemetry disabling option to transport:** an upcoming version of `@elastic/transport` will include the `x-elastic-client-meta` HTTP header that is used to capture some basic client telemetry. This change ensures the client's `enableMetaHeader` setting, which disables collecting this telemetry, is propagated to the transport.

## 9.1.0 [elasticsearch-javascript-client-9.1.0-release-notes]

### Features and enhancements [elasticsearch-javascript-client-9.1.0-features-enhancements]
Expand All @@ -30,6 +36,12 @@ To check for security updates, go to [Security announcements for the Elastic sta

- **Deep merge nested options on client instantiation:** If custom values for `redaction` and `headers` options were set by the user during `Client` instantiation, nested default values would be dropped rather than deep-merged. This has been fixed.

## 9.0.4

### Fixes [elasticsearch-javascript-client-9.0.4-fixes]

- **Propagate telemetry disabling option to transport:** an upcoming version of `@elastic/transport` will include the `x-elastic-client-meta` HTTP header that is used to capture some basic client telemetry. This change ensures the client's `enableMetaHeader` setting, which disables collecting this telemetry, is propagated to the transport.

## 9.0.3

### Fixes [elasticsearch-javascript-client-9.0.3-fixes]
Expand Down