Sourced from @​elastic/elasticsearch's releases.

v9.1.0

Changelog

v9.0.3

Changelog

v9.0.2

Changelog

v9.0.1

Changelog

v9.0.0

Changelog

v9.0.0-alpha.5

Changes from 9.0.0-alpha.4:

Serverless client merged back in

The @elastic/elasticsearch-serverless client is being deprecated, and its functionality has been merged back into this client. This should have zero impact on the way the client works, except that a new serverMode option has been added. When it's explicitly set to "serverless" by a user, a few default settings and behaviors are changed:

• turns off sniffing and ignores any sniffing-related options
• ignores all nodes passed in config except the first one, and ignores any node filtering and selecting options
• enables compression and TLSv1_2_method (same as when configured for Elastic Cloud)
• adds an elastic-api-version HTTP header to all requests
• uses CloudConnectionPool by default instead of WeightedConnectionPool
• turns off vendored content-type and accept headers in favor or standard MIME types

Docstrings for types that differ between stack and serverless have also been updated to indicate when that is the case.

v9.0.0-alpha.4

Changes from v9.0.0-alpha.3:

Parameter collation

Each API function's logic for deciding where in the request to put each passed parameter is now as follows:

1. if recognized as a body param from the spec, put it in the JSON body
2. if recognized as a path param, put it in the URL path
3. if recognized as a query param or a "common" query param (e.g. pretty, error_trace), put it in the querystring
4. if not recognized and this API accepts a JSON body, put it in the JSON body
5. if not recognized and this API does not accept a JSON body, put it in the querystring

The first two steps are identical to 8.x and prior 9.0.0 alpha releases. The last three steps replace the logic that put all unrecognized params in the querystring.

Parameter name list management

Each API function now only instantiates its arrays of accepted body/path/query param names once per client instance rather than during every function call, by moving the array values up to the constructor or module level, depending on which is available. Hopefully this introduces a small performance/memory improvement.

... (truncated)

• fa29021 9.1.0 changelog (#2940) (#2941)
• 5aa201f Auto-generated API code (#2936)
• 7e41af8 Auto-generated API code (#2927)
• 3d0a451 Bump to 9.1.0 (#2925)
• fe20f0a Checkout before npm publish unstable (#2919)
• 839dfc3 Update dependency chai to v5.2.1 (#2913)
• f644487 Update dependency @​types/node to v22.16.5 (#2912)
• 69c857f Auto-generated API code (#2915)
• e31816c Script redundancy cleanup (#2911)
• 72e58c6 Pin semver to latest minor release (#2910)
• Additional commits viewable in compare view

This version was pushed to npm by joshmock, a new releaser for @​elastic/elasticsearch since your current version.

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)