Skip to content

Commit fc8ce97

Browse files
authored
docs: Updated 1.2.0 changelog (#57)
1 parent 2343f0f commit fc8ce97

File tree

1 file changed

+36
-2
lines changed

1 file changed

+36
-2
lines changed

CHANGELOG.rst

Lines changed: 36 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,6 +2,40 @@
22
Changelog
33
=========
44

5+
1.2.0 (2023-11-23)
6+
------------------
7+
8+
This is a minor release bringing in minor new features and a few bug fixes,
9+
without any breaking changes.
10+
11+
Most changes are inherited by internally upgrading to version ``3.1.0`` of
12+
the ``c-questdb-client``.
13+
14+
Features
15+
~~~~~~~~
16+
17+
* ``Sender(..., tls=True)`` now also uses the OS-provided certificate store.
18+
The `tls` argument can now also be set to ``tls='os_roots'`` (to *only* use
19+
the OS-provided certs) or ``tls='webpki_roots'`` (to *only* use the certs
20+
provided by the ``webpki-roots``, i.e. the old behaviour prior to this
21+
release). The new default behaviour for ``tls=True`` is equivalent to setting
22+
``tls='webpki_and_os_roots'``.
23+
24+
* Upgraded dependencies to newer library versions. This also includes the latest
25+
`webpki-roots <https://github.com/rustls/webpki-roots>`_ crate providing
26+
updated TLS CA certificate roots.
27+
28+
* Various example code and documentation improvements.
29+
30+
Bug fixes
31+
~~~~~~~~~
32+
33+
* Fixed a bug where timestamp columns could not accept values before Jan 1st
34+
1970 UTC.
35+
36+
* TCP connections now enable ``SO_KEEPALIVE``: This should ensure that
37+
connections don't drop after a period of inactivity.
38+
539
1.1.0 (2023-01-04)
640
------------------
741

@@ -59,8 +93,8 @@ Features
5993
values. This has the same semantics as skipping the column altogether.
6094
Closes `#3 <https://github.com/questdb/py-questdb-client/issues/3>`_.
6195

62-
Bugfixes
63-
~~~~~~~~
96+
Bug fixes
97+
~~~~~~~~~
6498

6599
* Fixed a major bug where Python ``int`` and ``float`` types were handled with
66100
32-bit instead of 64-bit precision. This caused certain ``int`` values to be

0 commit comments

Comments
 (0)