v0.23.0

Highlights

• TLS for PostgreSQL and MySQL (#114, #115, #118, #117): libpq's sslmode and MySQL's --ssl-mode values, a CA file, a client certificate and key; the server's certificate checked against the CA file or the system's trusted certificates, by the profile's host also through an SSH tunnel; cancel requests and KILL QUERY encrypted too. Each connection says how it is encrypted (TLS 1.3, server verified), and a plain connection to another machine is a warning. See the README's TLS section.
• Existing prefer / PREFERRED profiles now try TLS first (without verifying the certificate): nothing breaks, the indicator changes. MySQL profiles without a mode are PREFERRED (except ones that pin a server public key).
• Behaviour changes to know: a PostgreSQL prefer profile now tries TLS, so a server that offers TLS but only TLS 1.0/1.1 (or a certificate key rustls refuses) is now an error instead of a plain connection (set disable); MySQL profiles without a mode default to PREFERRED; a MySQL login that needs the password itself over TLS whose certificate was not checked is refused to a server on another machine (use VERIFY_CA/VERIFY_IDENTITY, an SSH tunnel, or allow key retrieval).
• Tabs can be dragged to reorder them (#119).

The archives are for macOS and Linux (arm64 and x86_64) and Windows (x86_64); SHA256SUMS lists their checksums. The Windows build is untested: CI builds it and runs its tests, but nobody has used datarig on Windows yet.

What's Changed

• feat(tls): TLS settings, the tls crate and the encryption indicator by @DokaDev in #114
• feat(postgres): TLS connections by @DokaDev in #115
• feat(mysql): TLS connections by @DokaDev in #118
• feat(tabs): drag tabs to reorder them by @DokaDev in #119
• docs: TLS, and its tests in CI by @DokaDev in #117
• chore(release): 0.23.0 by @DokaDev in #120

Full Changelog: v0.22.0...v0.23.0