Skip to content

v1.1.2 — ssh-exec allows quoted wp flags; Kuma errors show their cause

Choose a tag to compare

@mwender mwender released this 15 Oct 20:19
· 74 commits to main since this release

A small fix release. spinuptui ssh-exec stops refusing a harmless WP-CLI read, and a failed Uptime Kuma connection now tells you why it failed.

Fixed

  • A quoted wp command that ends in a flag is allowed. spinuptui ssh-exec <site> -- bash -c 'wp --info' was denied because the closing quote landed on the flag and the guard read it as an option missing its value.
  • Uptime Kuma connection errors show the actual reason. With a long instance URL, the cause (a TLS, DNS or proxy problem, say) ran past the edge of the connect form, leaving only Couldn't reach Uptime Kuma at https://…:. The error lines in the connect form and the Alerts panel now wrap. If you couldn't connect before, update and try again: the message should now say what went wrong.

Update: brew upgrade spinuptui (Homebrew), bun add -g spinuptui@latest --no-cache (npm install) or git pull in your checkout (a linked global spinuptui picks it up immediately). New to SpinupTUI? brew install mwender/tap/spinuptui.

Full changelog: v1.1.1...v1.1.2