v0.10.4

The connect form no longer asks about TLS.

What changed

The last step of the connect form used to be "Skip TLS certificate verification?" with No preselected. Safe by default, but it asked people to make a security decision at the one moment they had the least information to make it with, and the only hint under it read "only for self-signed certs". That never said what answering yes actually costs: your token or password goes out on every request over a connection nothing authenticates.

Certificates are now always verified, and the form ends at the credential.

When a certificate is rejected

Instead of echoing the HTTP client's wording, you get a line that names both fixes:

TLS certificate rejected. Add the server's CA to your trust store, or set
insecure_skip_verify = true in config.toml

The first of those is the real fix and works for every other tool on your machine at the same time. If your organisation runs TLS inspection, that root is often already installed on a managed laptop, so check there first.

That message runs 116 characters, so the message row now grows to two lines when an error is wider than the terminal. Otherwise the half naming the setting is exactly the half that gets clipped.

Also

insecure_skip_verify is config-only now, and reconnecting no longer rewrites it. A value you set by hand survives pressing A, which was not true before.

Upgrading

brew update && brew upgrade lazygocd

brew update matters. Homebrew refreshes a tap at most once a day, so without it brew upgrade can report an older version as already the latest.