From 7826b1b401137b11ca8faebd683e3e6ea25c9ce9 Mon Sep 17 00:00:00 2001 From: spalger Date: Mon, 3 Apr 2017 18:38:58 -0700 Subject: [PATCH] [changelog] update --- docs/changelog.asciidoc | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/docs/changelog.asciidoc b/docs/changelog.asciidoc index 2606cb23e..d3aac5925 100644 --- a/docs/changelog.asciidoc +++ b/docs/changelog.asciidoc @@ -1,11 +1,12 @@ [[changelog]] == Changelog -=== 13.0.0-beta1 (Feb 14 2017) +=== 13.0.0 (Apr 4 2016) - * apiVersion `"5.2"` is now the default + * apiVersion `"5.3"` is now the default * Fixed the way that http addresses are sniffed from the cluster https://github.com/elastic/elasticsearch-js/issues/496[#496] * Switched back to `agentkeepalive` for managing keep-alive connections https://github.com/elastic/elasticsearch-js/issues/476[#476] + * `keepAlive*` settings have changed, and the defaults have been updated to match node.js/agentkeep defaults https://github.com/elastic/elasticsearch-js/commit/87cc201c0693a30953033c7d15dd4019f61b2b0f[87cc201] * `bulk` and other APIs that send line-delimited JSON bodies now use the `Content-Type: application/x-ndjson` header https://github.com/elastic/elasticsearch-js/pull/507[#507] * minor changes to `apiVersion` will no longer be released as a major release ** When we decided to have elasticsearch-js support multiple version of Elasticsearch, we included an `apiVersion` configuration paramter for users to choose the API that each client should expose. This setting had a default value that matched the most recent version of Elasticsearch at the time of release. Since Elasticsearch didn't make specific guarantees about backwards compatibility elasticsearch-js released a new major version every time the default `apiVersion` changed.