Skip to main content

Release 0.1.147

Every open branch now takes new commits from main, even while an agent is working in it. When you say Yes to an agent's scenario change, it is written straight away, and agents can now ask to remove a scenario. Modules can be implemented again from the dialog, and you can check a page for accessibility problems from Repave IDE.

Upgrade notes​

  • Database migrations run automatically during the upgrade. They record why a scenario changed and when a branch's unit tests are still to be checked.
  • No changes to .env or docker-compose.yml.

New​

Check a page for accessibility problems from Repave IDE. /repave:a11y-scan runs the same check as the Accessibility button on a feature's preview, explains each problem in plain words, worst first, fixes the ones you choose and scans again. repave a11y scan runs the check alone. When Repave builds or changes screens, its agent now runs the check on each one and fixes the critical and serious problems.

Agents can ask to remove a scenario the legacy app never reaches, such as a screen nothing opens. Yes, remove it takes it out of the To-Be and the feature file, and the run stops building and testing it; No, keep it means it is built and tested.

Implement a feature again from the module. The Implement module dialog lets you choose the model, and lists features that are already implemented, Awaiting Write Tests or Verified unticked. Tick one to implement it again; its results are cleared and it needs Write Tests again.

The Modules page has a Verified column, counting each module's features that are past UAT.

Improvements​

Every open branch takes main's new commits. When main moves, a running implementation, prototype or verification pauses, takes the new commits and carries on, told what came in, whether or not automatic stacking is on. Uncommitted changes nobody has open in Repave IDE are set aside and put back. A feature's Merge <base> button reads Merging… while that happens instead of being disabled. New commits on main are noticed within a minute, and main is fetched every five minutes.

A Yes to a scenario change is written at once. The question shows the scenario as it stands, Current, beside the agent's Proposed text. After you answer, it reads Written to the To-Be, or Not written with the reason, and the scenario's history keeps your question as Why it changed.

Unit tests of a branch that builds on unfinished work are checked when it lands, not while what it builds on is unfinished; the job log says so. Create PR, Merge and module delivery run the check once that work has merged. A test fix that changes nothing on its next try now stops and shows you the failure, and a test run that cannot finish, such as one that runs out of memory, fails with the reason.

Retry on a module run takes only the features it left unimplemented, and says "Nothing to retry: every feature in this run is implemented." when there are none.

Write Tests uses the scenarios as they read now. If a feature's scenarios changed after it was implemented, Write Tests first writes them to the feature file, so the tests match.

Fixes​

  • Apply UI prototype on a module's feature could mark it failed, so the module offered to implement it again; it also left a failed apply's edits behind, and could add a second trace start that broke every test. The feature keeps its status, a failed apply's edits are taken back, and your test setup is left alone.
  • A module could be delivered without a feature whose work was still on its own branch. Delivery now offers Move work onto <module> and deliver.
  • A module's features on their own branches waited for each other's builds and implementations before the module had its own branch.
  • An agent waiting for your answer could take an update from what it builds on as your No. A resumed Write Tests on a module no longer checks features it already judged.
  • An agent could start with no task when it was paused seconds after starting, and the feature was marked failed.
  • Staging could fail with "fatal: not a git repository" after a worktree clean-up in Repave IDE; the staging copy now repairs itself.