Skip to content

Releases: elastic/elastic-transport-python

8.13.1

28 May 07:00
v8.13.1
06dba73
Compare
Choose a tag to compare
  • Fixed requests 2.32 compatibility (#164)
  • Fixed TypeError when two nodes are declared dead at the same time (#115, contributed by @floxay)
  • Added TransportApiResponse (#160, #161, contributed by @JessicaGarson)

8.13.0

27 Mar 06:20
v8.13.0
f42ec04
Compare
Choose a tag to compare
  • Support the HTTPX client with asyncio (#137, contributed by @b4sus)
  • Added optional orjson serializer support (#152)

8.12.0

19 Jan 08:54
v8.12.0
d85d0cf
Compare
Choose a tag to compare
  • Fix basic auth built from percent-encoded URLs (#143)

8.11.0

13 Dec 07:11
v8.11.0
09e8823
Compare
Choose a tag to compare
  • Always set default HTTPS port to 443 (#127)
  • Drop support for Python 3.6 (#109)
  • Include tests in sdist (#122, contributed by @parona-source)
  • Fix __iter__ return type to Iterator (#129, contributed by @altescy)

8.10.0

30 Oct 05:14
v8.10.0
65424ca
Compare
Choose a tag to compare
  • Support urllib3 2.x in addition to urllib3 1.26.x (#121)
  • Add 409 to NOT_DEAD_NODE_HTTP_STATUSES (#120)

8.4.1

25 Sep 20:02
17338aa
Compare
Choose a tag to compare
  • Fixed an issue where a large number of consecutive failures to connect to a node would raise an OverflowError.
  • Fixed an issue to ensure that ApiResponse can be pickled.

8.4.0

25 Aug 16:52
Compare
Choose a tag to compare
  • Added method for clients to use default ports for URL scheme.

8.1.2

19 Apr 18:29
Compare
Choose a tag to compare
  • Fixed issue when connecting to an IP address with HTTPS enabled would result in a ValueError for a mismatch between check_hostname and server_hostname (#81)

8.1.1

30 Mar 22:40
Compare
Choose a tag to compare

Fixed

  • Fixed JsonSerializer to return None if a response using Content-Type: application/json is empty instead of raising an error.

8.1.0

09 Mar 20:09
Compare
Choose a tag to compare

Fixed

  • Fixed Urllib3HttpNode and RequestsHttpNode to never require a valid certificate chain when using ssl_assert_fingerprint. Instead the internal HTTP client libraries will explicitly disable verifying the certificate chain and instead rely only on the certificate fingerprint for verification.