cli@1.3.0

the-dev-tools/dev-toolscli@1.3.0Oct 9, 2026by github-actions[bot]

Upgrading?

AI Summary

The CLI update introduces advanced load testing modes including ramping VUS and arrival rates, along with configuration rules for thresholds and aborts. It also adds streaming metrics reporting and support for scaling load profiles across multiple machines.

Key Highlights

  • Expanded load modes: `ramping-vus`, `constant-arrival-rate`, and `ramping-arrival-rate`
  • Added `load:` configuration entry for `think_time`, `thresholds`, and `abort` rules
  • Added `--report frames:<url>` to stream metrics frames and final report to an HTTP endpoint
  • Added `--vus-scale` and `--rate-scale` flags to split load profiles across machines

New Features

  • New load modes: `ramping-vus` (graceful ramp-down), `constant-arrival-rate`, and `ramping-arrival-rate`
  • `load:` configuration block with `think_time` and `thresholds` (e.g., p95 < 300ms) for each step
  • `abort` rules evaluated every metrics frame to stop runs early with exit code 108
  • `--report frames:<url>` for streaming HDR histograms and final reports
  • `--load-file` to read scenarios from a separate configuration file

Full Release Notes

## 1.3.0 (2026-10-09)

### 🚀 Features

- Load mode grows from constant-vus to four executors: `ramping-vus` (stages with graceful ramp-down), and the open-model `constant-arrival-rate` and `ramping-arrival-rate`, which start iterations on schedule whatever the response time and report dropped iterations once `max_vus` are busy. A `load:` entry can add `think_time`, `thresholds` (e.g. `p95: <300ms`, `errors: <1%`, per step under `steps:`), checked at the end and failing the run with exit code 99, and `abort` rules evaluated every metrics frame that stop a run early with exit code 108. `--report frames:<url>` streams every metrics frame, with per-step HDR histograms, and the final report to an HTTP endpoint (bearer token from `DEVTOOLS_FRAMES_TOKEN`, retried in the background, and the run stops if the endpoint is unreachable for 60s); `--vus-scale`/`--rate-scale` split one profile across machines, `--load-file` reads scenarios from a separate file with the same schema, and the summary now shows the request count it is based on. ([c5002b3d](https://github.com/the-dev-tools/dev-tools/commit/c5002b3d))

### ❤️ Thank You

- moosebay

Related Repositories