Skip to content

Resolvr v0.3.0

Choose a tag to compare

@github-actions github-actions released this 30 Sep 14:02
· 2 commits to main since this release

Resolvr 0.3.0

Flows grow up: one scenario runs on anyone's data, a whole set runs in one command, and a workspace can refuse writes.

Variables and constants

A step used to need a first request just to find the id of your own client, so the same scenario could not be reused by another person or run against a list of clients.

A flow now carries Constants — the starting context, available to steps as {{name}} — and a run may pass its own values on top:

flow_run(workspaceId, flowId, variables: { clientId: "…" })

Run values win over constants. Constants are expanded once per run, so {{$uuid}} in a constant is one identifier for the whole flow.

Value generators

Templates — step variables, headers, constants — understand generators: {{$uuid}}, {{$timestamp}}, {{$unix}}, {{$isoDate}}, {{$date}}, {{$randomInt}} ({{$randomInt:1:100}}), {{$randomString}} ({{$randomString:12}}) and {{$randomEmail}}. Without them a second run of a flow with idempotency keys, emails or other unique fields failed on the values left behind by the first.

Protection against accidental writes

A workspace named “development” may well point at a production API, and until now only a hook on the agent's side stood in the way. Workspace settings now offer Protection:

  • Confirmation for every mutation — the app asks before a mutation or a flow run; through MCP run, flow_run and flow_run_many refuse the call until the agent passes confirm: true, which it should do only after asking you.
  • Read only — mutations are refused, confirmation or not.

The check lives in the run engine, so it holds for manual work, for flow steps and for agents alike. Reads are never restricted, and the current mode is visible in workspace_list.

A whole set in one command

MCP flow_run_many runs a set of flows selected by id prefix (smoke-billing-), by tag or by an explicit list — sequentially, or in parallel when the scenarios are independent. The answer is a table: outcome, duration and the step a flow stopped at. A failing flow does not cancel the rest, because a regression run is only useful whole.

The registry lives with the flows

A flow carries Tags and Preconditions, so the list of smoke tests no longer lives in a separate document that drifts away from them. The outcome of every run is kept outside the repository, so running a flow never produces a diff: flow_list reports lastGreenAt, and in the sidebar a flow that passed is marked with a ✓ and the date.

Checks and step errors

  • eqNum compares numbers regardless of notation, so "10.000000" equals 10 — money-like fields arrive as strings, and strict eq used to fail on them.
  • len checks the length of an array, a string or the number of object fields.
  • A step result carries the response errors even when the step is green: with Any response the GraphQL errors inside an HTTP 200 body used to stay invisible.

Parallel agents

operation_get and flow_get return a version — a fingerprint of the file contents. Passing it back as expectedVersion to operation_save or flow_save turns a silent overwrite into a refusal when someone has changed the file in the meantime. Without the field, writes behave as before.

Everything else is identical to 0.2.9.

Downloads

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