Skip to content

v0.7.1 (bêta)

Pre-release
Pre-release

Choose a tag to compare

@gnocent gnocent released this 18 Oct 21:05
· 31 commits to main since this release

TermDevTools v0.7.1 (beta)

Version française : CHANGELOG_fr.md

In one sentence: a bug-fix release — Ctrl+E on a request line still being typed no longer sends the request above it, and a new connection no longer fails on Linux because of the certificate directories (#2).

Fixes

  • An incomplete request line no longer runs the request above it: Ctrl+E on a line such as GET still being typed sent the closest request above, a DELETE for instance. Nothing is sent now, and the status bar says no request was found. A blank or comment line between two requests still runs the one above.
  • A new connection no longer fails on Linux because of the certificate directories: default_ca_dir and default_client_cert_dir filled the certificate fields of a new connection with a directory, which was then loaded as a file — even in http, where those fields are hidden. They now only set where the certificate picker starts.
  • TLS files are only read when they are used: the CA file only for https with verification on, the client certificate only for https. A path saved for a cluster in http, or with verification off, no longer blocks the connection. The command of F9 follows the same rule.
  • Two exports in the same second no longer overwrite each other: the file name now ends with a random number (YYYYMMDD-HHMMSS-<number>.json).
  • F7 while the _cat columns are being fetched: an answer from before the reload no longer replaces the new columns.

Thanks to @fbaligand for the report (#2) and to @amineamanzou for the fixes (#5, #7).

Before upgrading from 0.7

  • Nothing to do: config.yaml is read as before.
  • New connection: the certificate fields now start empty; pick the file with the certificate picker, which opens in default_ca_dir or default_client_cert_dir. Saved connections keep their paths.
  • Exports: a script that relied on the old file name (YYYYMMDD-HHMMSS.json) must allow for the new suffix.

Checks

  • go vet and go test ./... pass, run on Windows: unit tests, and end-to-end tests of the interface on a simulated screen.
  • The fixes were not tried against a real cluster: none of the test clusters uses TLS. The reference data (recipes, endpoints, _cat columns) has not changed since 0.6, and its checks against eleven real clusters are those of 0.6.
  • govulncheck: no known vulnerability, neither in the dependencies nor in the standard library of Go 1.27.2, which the binaries are built with.
  • No independent external audit was carried out.

Known limits

  • go install does not work with this version: its module path is not yet the repository's. It does from v0.7.2 on (#1); with this version, use the binaries below.
  • The limits of 0.7 still apply: see the changelog.

Binaries

One self-sufficient file per platform — no archive and no companion file:

  • termdevtools-linux-amd64 — Linux x86-64 (static binary)
  • termdevtools-windows-amd64.exe — Windows 10/11 x64
  • termdevtools-darwin-arm64 — macOS Apple Silicon
  • SHA256SUMS — SHA-256 checksums of the three files

Download the file for your platform and SHA256SUMS, check it (sha256sum -c SHA256SUMS --ignore-missing on Linux), make it executable (chmod +x, Linux and macOS), run it: termdevtools --version answers termdevtools v0.7.1. The binaries are not signed. Step by step, platform by platform: INSTALL.md (français).