Release notesedit
8.13.1edit
Fixesedit
Pin @elastic/transport to ~8.4.1
edit
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 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.
8.13.0edit
Featuresedit
Support for Elasticsearch v8.13.0
edit
You can find all the API changes here.
Fixesedit
Ensure new connections inherit client’s set defaults #2159edit
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.
8.12.3edit
Fixesedit
Bump @elastic/transport to ~8.4.1
edit
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 elastic/elastic-transport-js#91 for details.
8.12.2edit
Fixesedit
Upgrade transport to 8.4.1 #2137edit
Upgrades @elastic/transport
to 8.4.1 to resolve a bug where arrays in error diagnostics were unintentionally transformed into objects.
8.12.1edit
Fixesedit
Fix hang in bulk helper semaphore #2027edit
The failing state could be reached when a server’s response times are slower than flushInterval.
8.12.0edit
Featuresedit
Support for Elasticsearch v8.12.0
edit
You can find all the API changes here.