mr-onion

Changelog

What changed in Mr Onion, for someone using it. Each entry links the decision record behind it; docs/decisions/README.md indexes them all.

Versioning (TFP-257, decided 2026-10-27): semantic versioning, below 1.0 while the report format can still change. The minor version goes up when a phase completes; the patch version for fixes between phases. 1.0 comes when the report and the CI command are declared stable, after Phase 47.

Unreleased

Changed

Fixed

[0.4.0] — 2026-11-13

Mr Onion in your pipeline (Phase 47)

Mr Onion can run as one step of another project’s CI. It crawls the site, generates the suite and runs it, then ends with an exit code the pipeline acts on (Phase 47; the guide is docs/CI_INTEGRATION.md).

Security

0.3.0 — 2026-11-12

Renamed: TestForge is now Mr Onion (0.3.0)

The app, its reports, the command, the settings, the data folder, the GitHub repo and the Claude Code plugin all take the new name (Phase 48). Ticket and test IDs, saved runs, baselines and site suites are unchanged.

Security

Changed

Fixed

0.2.0 — 2026-10-31

The first tagged version.

Which TestForge found this

Security

Fixed

Run speed and honest capped runs (Phase 39)

[0.1.0] — untagged starting point

Not tagged (owner decision, 2026-10-28): Phase 39 completes before the version stamp lands, so the first tag is v0.2.0. This entry stays as the baseline it describes.

Everything built from Phase 16 to Phase 42, except Phase 39 (above). Before this, Phases 1–15 (April 2026) moved TestForge from a FastAPI backend to Next.js (history).

Security

Running a site

What gets tested

Reports and history

Reuse instead of regeneration

Generation

Also