Resolvr v0.2.8

Resolvr 0.2.8

Negative tests in flows, and better crash diagnostics.

Negative tests in flows

A flow step used to pass only when the server answered without errors — so a check like "without a token the API refuses" failed on the very error it expected and stopped the flow.

Each step now has an Expected result:

• Success — the default, as before: a response without errors, and the checks pass.
• Error — the server returns an error (HTTP not 2xx or GraphQL errors), and the checks pass. The flow goes on to the next step. If the request unexpectedly succeeds, the step fails.
• Any response — only the checks decide.

With Error, add a check that pins down which error you expect — for example errors.0.message contains Unauthorized, or errors.0.extensions.code equals FORBIDDEN — otherwise any failure, including a server crash, would count. Agents set the same field through MCP flow_save (expect).

Crash diagnostics

Release builds now keep the symbol table, so a native crash backtrace (gdb, system crash reports) names the function instead of showing ???. This helps track down a rare crash on Linux. The app is about 1.5 MB larger.

Everything else is identical to 0.2.7.

Downloads

Platform	File
macOS (Apple Silicon + Intel)	Resolvr_0.2.8_universal.dmg — not notarized; on first launch right-click → Open
Linux	Resolvr_0.2.8_amd64.AppImage, Resolvr_0.2.8_amd64.deb, Resolvr-0.2.8-1.x86_64.rpm
Windows	Resolvr_0.2.8_x64-setup.exe, Resolvr_0.2.8_x64_en-US.msi