Skip to main content

Release 0.1.155

Verify on legacy app now records Proof for the legacy desktop app (its screens, SQL, web service calls and data changes), shown beside the new app's. Storybook projects can follow a design system kept in its own repository, and a document regenerated after its template changed now follows the new template.

Upgrade notes​

  • Two database migrations run on upgrade. They only add new data; nothing existing is changed.
  • A new image, legacy-recorder, ships with this release. It runs beside the legacy app during Verify on legacy app and records the app's SQL and web service calls. The upgrade sets LEGACY_RECORDER_IMAGE in .env and pulls the image; an airgapped bundle includes it as images/legacy-recorder-<version>.tar.gz. docker-compose.yml passes the new setting to the app.

New​

Proof for the legacy desktop app. Every Verify on legacy app records, for each As-Is scenario it checks, each step's screen, the SQL the app sent, the web services it called and the rows it changed. Open it from the Proof button on the As-Is scenario. On the To-Be tab, a scenario's Proof shows the new app's record beside the legacy app's under New app and Legacy app. SQL Server and Oracle are supported, including Oracle connection strings in ODBC form. Recording SQL and data changes needs a few database rights; when one is missing, the Proof says which. The legacy app page lists them.

A design system from its own repository, in Storybook mode. In Settings, under Prototype Mode, Design system repository names a design system that lives in its own repository. Saving one sets Storybook up again: a published package is installed, and every story built afterwards uses the design system's components and follows its guidance. A repository your GitHub token cannot read is refused when you save; a token that cannot read the package fails setup and asks for the read:packages scope, with Retry.

Improvements​

  • In a scenario's Proof, each step's screen now sits on its step in the Activity table, which opens unfolded.
  • What the test run recorded shows Passed or Failed beside its heading. The Test Replay tab plays that record's run, so it always matches the evidence you are reading.

Fixes​

  • Regenerating a document after uploading a new template for its type kept the old version's sections. The next version now follows the new template's outline, keeping the facts. Changing only the cover, header or footer still updates the document in place.