Ultraman 0.4.0

Ultraman 0.4.0, with Node v24.22.2 inside.

macOS and Linux: curl -fsSL https://ultraman-app.github.io/install.sh | sh
Windows (PowerShell): irm https://ultraman-app.github.io/install.ps1 | iex

Downloaded from a browser instead, Windows and macOS warn that the app isn't signed: see the page.

What's new

Reading and building pipelines

• Step rows name their request (login POST /auth/login), show its description and, after a run or a Send, the HTTP status (201 · 1.7 ms).
• The assert and extract forms offer the requests before the step instead of typing $name, and show only the fields each check uses, with a line on what it compares.
• The diagram's data arrows reach every field a step uses, asserts included.
• Add step says what each kind of step does, adds a request from a collection (linked, with its checks) and inserts between steps with the + that shows on hover.

Checks

• New checks: exists, notExists, notEquals, greaterThan, matches (with flags, /^ord_/i), type and schema (JSON Schema, inline or a file, with format), and a header selector for asserts and extracts.
• The menu over a response value also asserts that it exists or its type; each response header can be asserted from the Headers tab.
• Generate checks proposes a set from the response on screen, and a banner warns when a response's shape changed since the last send (a field gone, a type changed).
• A check just added reads "not run yet" until the next Send.

Environments and secrets

• An Environments panel: create, duplicate, rename and delete environments, with shared values (git), this machine's current values and secret variables kept in the vault (the file holds only a reference). Import .env brings a file in as current values.
• The eye next to the selector shows the environment and the session (what each step extracted, who uses it), with clear.
• A missing value can be saved in the environment or the vault from the dialog that asks for it.
• The host shows its variables as chips ({{env.api}}), and a response says when it was sent with another environment.
• A Send reads the vault like a run does: a saved secret doesn't travel in the request.
• An environment can carry request options: plain HTTP for an internal service and a custom CA for one with its own certificate, under what a pipeline or a request sets.

Collections

• Run a whole collection or folder from its menu: the login once, then each request with its checks, without creating a pipeline. The results list each request, and past runs can be opened again.

Navigation

• Filters in the sidebars, Ctrl+P to open any pipeline, block or request, tag chips, Ctrl+N, Ctrl+W, Ctrl+Tab and a list of shortcuts on ?.
• The app's own dialog asks before discarding unsaved work, with Save, Discard and Cancel.
• Open a run file (or drop one) to look at a run saved elsewhere, such as in CI; Watch in the Runs strip reruns the pipeline on change or every few minutes.

Command line

• ultraman run --all, --tag X, --collection ID, --bail, --junit FILE for CI, and --watch / --every 5m with a system notification when a run fails or passes again.
• --parallel N runs up to N of the selected pipelines at once; each prints whole when it ends.
• ultraman mock serves the history's recordings as a fake API, from the command line or the Requests area. It can forward what has no recording to the real API (--proxy), answer a route's recordings In order (--sequence) or keep one pinned, and it only answers pages on this machine unless --expose.

Ultraman 0.3.0

Ultraman 0.3.0, with Node v24.22.2 inside.

macOS and Linux: curl -fsSL https://ultraman-app.github.io/install.sh | sh
Windows (PowerShell): irm https://ultraman-app.github.io/install.ps1 | iex

Downloaded from a browser instead, Windows and macOS warn that the app isn't signed: see the page.

What's new

• Ultraman tells you when there's a newer version. A card in the bottom-left corner shows the version, What's new and the command that updates. Not now hides it until the next one. To know, it asks GitHub for the latest release once a day; ULTRAMAN_NO_UPDATE_CHECK=1 turns that off.
• The desktop app updates itself. Update and restart downloads the new version, checks its signature (only a build signed with Ultraman's updater key installs), installs it and restarts. It waits until your changes are saved and nothing is running. The ultraman command comes along.
• Coming from 0.2.0 or earlier: update by hand this once, with the command above (close Ultraman first). From 0.3.0 on, the app does it.

Ultraman 0.2.0

Ultraman 0.2.0, with Node v24.22.2 inside.

macOS and Linux: curl -fsSL https://ultraman-app.github.io/install.sh | sh
Windows (PowerShell): irm https://ultraman-app.github.io/install.ps1 | iex

Downloaded from a browser instead, Windows and macOS warn that the app isn't signed: see the page.

What's new

• Your saved secrets are locked with a master password. Nothing on disk opens them anymore, so a program that copies ~/.ultraman gets nothing it can use. Only the Ultraman window, or a terminal where you type the password, can unlock them.
• Coming from 0.1.0: the first time a run needs a saved secret, Ultraman asks you to choose a master password and moves your secrets into the vault. If you forget it, the secrets can't be recovered.
• Remember on this machine (off by default) keeps the password in the system keychain so the app opens without asking. The checkbox says what that costs on your system.
• ultraman run and ultraman secret ask for the master password in the terminal. In CI, keep passing secrets as ULTRAMAN_SECRET_<NAME>: no password needed. New: ultraman secret password changes it.
• Signed releases: the install scripts now install only a release whose SHA256SUMS is signed with Ultraman's release key.

Ultraman 0.1.0

Ultraman 0.1.0, with Node v24.22.2 inside.

macOS and Linux: curl -fsSL https://ultraman-app.github.io/install.sh | sh
Windows (PowerShell): irm https://ultraman-app.github.io/install.ps1 | iex

Downloaded from a browser instead, Windows and macOS warn that the app isn't signed: see the page.