v0.14.2

In this release an issue is fixed that was reported in #150 and #166. The issue was that mutual TLS (mTLS), aka. two-way TLS, was enforced when configuring TLS via the TLSConfig object, but sometimes the users needed to have normal one-way TLS, for example in Schema Registry config. Now the TLSConfig object can be used in three different ways:

1. Enabling TLS to just use system certificates:

const tlsConfig = {
    enableTls: true,
    insecureSkipTlsVerify: false,
    minVersion: TLS_1_2,
};

2. Enabling one-way TLS using a custom server certificate:

const tlsConfig = {
    enableTls: true,
    insecureSkipTlsVerify: false,
    minVersion: TLS_1_2,
    serverCaPem: "/path/to/your/server-ca.pem",
};

3. Enabling two-way mTLS using a custom server certificate and client certificate and key files:

const tlsConfig = {
    enableTls: true,
    insecureSkipTlsVerify: false,
    minVersion: TLS_1_2,
    serverCaPem: "/path/to/your/server-ca.pem",
    clientCertPem: "/path/to/your/client-cert.pem",
    clientKeyPem: "/path/to/your/client-key.pem",
};

What's Changed

• Fix bug in TLS config handling by @mostafa in #170
• Update README and API docs by @mostafa in 09675bc f62f7ab 293f1f0
• Update dependencies to latest version by @mostafa in e066e68

Full Changelog: v0.14.1...v0.14.2