v0.19.0

Examples anyone can run: the test server as a Docker image, and a guided tour of every feature.

Highlights

The test server in Docker

The complete example project, docs/example, runs against a small test server: bearer and API-key auth, Basic, OAuth2, cookie sessions, forms and uploads, slow responses and async jobs. It used to need the .NET SDK. It is now an image:

docker run --rm -p 127.0.0.1:5122:5122 ghcr.io/kikutano/tinyprobe-testserver:0.19.0
tinyprobe run docs/example/workflows -e docs/environment.yaml

The server accepts fixed credentials and fake tokens on purpose: keep the 127.0.0.1: in -p so only your machine reaches it. Images for linux/amd64 and linux/arm64, tagged like the tinyprobe image (0.19.0, 0.19, latest).

A guided tour of docs/example

docs/example/README.md walks through the format one workflow at a time: what each one shows, and the commands to try (call, --to, --junit, inspect, a validation error on purpose, init), and the Postman and OpenAPI files to try a migration with your agent.

The suite now covers the whole format. A new workflow, jobs.yaml, starts a report and waits for it with until, with generated values and workflow variables:

variables:
  reportName: "report-${$uuid}"      # resolved once per run: every step sees the same name
  requestedAt: ${$now}

steps:
  - call: start_report
    with: { name: "${reportName}", requestedAt: "${requestedAt}" }
    save: { reportId: $.id }
  - call: get_report
    with: { id: "${reportId}" }
    until:
      body: { $.status: done }
      every: 100ms
      timeout: 10s

catalog.yaml adds AND and OR (any) checks.

Also

• No change in the format, the CLI or the protocol: the tinyprobe binary does what 0.18.0 did.
• The VS Code extension 0.8.0 follows, with sequence files, go to definition and the items of for_each steps.

No breaking changes.

What's Changed

• Examples anyone can run: test server image and guided docs/example (M4-12) by @kikutano in #32

Full Changelog: v0.18.0...v0.19.0